git-operations
Git version control operations including status, branches, commits, diffs, and worktree management. Use when working with git repositories, reviewing changes, or managing branches.
When & Why to Use This Skill
This Claude skill provides a comprehensive suite of Git version control operations, enabling seamless repository management directly within the AI interface. It streamlines essential developer workflows including status tracking, branch management, code diffing, and commit execution, ensuring efficient version control and project organization.
Use Cases
- Repository Status & Health Checks: Quickly monitor staged, unstaged, and untracked files to maintain a clear overview of the current development state.
- Streamlined Branching Workflows: Create, list, and switch between branches to manage feature development and bug fixes without leaving the workspace.
- Code Review and Change Analysis: Use detailed diff and log tools to audit recent modifications, review staged changes, and ensure code quality before committing.
- Atomic Commit Management: Create well-documented commits using conventional formats and manage work-in-progress changes with stash operations.
- History and Authorship Tracking: Inspect commit history and use 'git blame' to understand the evolution of the codebase and identify authorship for specific changes.
| name | git-operations |
|---|---|
| description | Git version control operations including status, branches, commits, diffs, and worktree management. Use when working with git repositories, reviewing changes, or managing branches. |
| allowed-tools | Bash, Read, Write |
Git Operations Skill
Version: 1.0.0 Purpose: Git version control operations for repository management
Triggers
| Trigger | Examples |
|---|---|
| Status | "git status", "check changes", "変更確認" |
| Branch | "list branches", "create branch", "ブランチ一覧" |
| Commit | "commit changes", "view commits", "コミット" |
| Diff | "show diff", "review changes", "差分確認" |
Integrated MCP Tools
This skill wraps the following MCP tools from miyabi-mcp-bundle:
| Tool | Purpose |
|---|---|
git_status |
Repository status with staged/unstaged files |
git_branch_list |
List all branches with details |
git_current_branch |
Get current branch name |
git_log |
Commit history (configurable limit) |
git_diff |
Unstaged changes diff |
git_staged_diff |
Staged changes diff |
git_remote_list |
Remote repositories |
git_worktree_list |
Git worktrees |
git_stash_list |
Stashed changes |
git_tag_list |
Repository tags |
git_blame |
Line-by-line authorship |
git_show |
Commit details |
git_branch_ahead_behind |
Branch sync status |
git_commit_create |
Create new commit |
git_branch_create |
Create new branch |
git_checkout |
Switch branches |
git_merge |
Merge branches |
git_stash_save |
Save changes to stash |
git_stash_pop |
Restore stashed changes |
Workflow
Phase 1: Repository Assessment
Step 1.1: Check Status
Use git_status to see:
- Current branch
- Staged files
- Unstaged modifications
- Untracked files
Step 1.2: Review Recent History
Use git_log with limit=10 to see recent commits
Phase 2: Change Review
Step 2.1: Unstaged Changes
Use git_diff to see uncommitted changes
Step 2.2: Staged Changes
Use git_staged_diff to review what will be committed
Phase 3: Commit Workflow
Step 3.1: Stage Files
git add <files>
Step 3.2: Create Commit
Use git_commit_create with:
- message: Conventional commit format
- author: Optional override
Best Practices
✅ GOOD:
- Review diff before committing
- Use conventional commit messages
- Keep commits atomic and focused
❌ BAD:
- Commit without reviewing changes
- Large commits with mixed concerns
- Vague commit messages
Checklist
- Repository status checked
- Changes reviewed (diff)
- Commit message follows convention
- Tests pass before commit