2.5 KiB
2.5 KiB
name, description
| name | description |
|---|---|
| git-expert | Git operations, history exploration, and intelligent commit management. Use when users ask about git history ("what did we change", "when did we add"), want to understand past changes, need help with commits ("commit this", "save my work", "checkpoint"), ask about branches, or mention recent work. |
Git Expert Skill
Git operations, history exploration, and intelligent commit management.
Capabilities
History Analysis
- Search commit messages and code changes
- Trace file history to understand evolution
- Find when specific code was introduced or removed
- Identify who made changes and why
Smart Commits
- Create well-formatted Conventional Commits
- Split large changes into atomic commits
- Handle pre-commit hooks gracefully
- Never commit secrets or sensitive data
Session Awareness
- Track what was done during the current session
- Show uncommitted work
- Create checkpoints before risky operations
Tools Available
Use the git-intelligence MCP server tools:
get_recent_commits- Recent commit historysearch_commits- Search by message or codeget_status- Current repository stateget_diff_summary- Summary of changes
For file history and branch info, use Bash:
git log --oneline -10 -- <filepath>- File-specific historygit branch -a- Branch information
Commit Format
Always use Conventional Commits format:
<type>(<scope>): <subject>
Type mappings:
| Type | Use for |
|---|---|
| feat | New feature |
| fix | Bug fix |
| docs | Documentation |
| style | Formatting |
| refactor | Refactoring |
| perf | Performance |
| test | Tests |
| build | Build system |
| ci | CI/CD |
| chore | Maintenance |
| revert | Revert |
Best Practices
- Before editing: Check recent commits to understand context
- Before committing: Review all changes, never blind commit
- Large changes: Suggest splitting into atomic commits
- Unclear intent: Ask user for commit scope/description
- Secrets detected: Warn and refuse to commit
Example Interactions
User: "What changed in the auth module recently?"
- Use
search_commitswith query "auth" or Bashgit log --oneline -10 -- src/auth/
User: "Commit my changes"
- Run
get_status, review diffs, create appropriate conventional commit
User: "What did we do this session?"
- Check recent commits and current diff, summarize activity
User: "Save my work before I try this"
- Create a checkpoint commit with current context