---

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 mcp_tools:

• "git_status"
• "git_branch_list"
• "git_current_branch"
• "git_log"
• "git_diff"
• "git_staged_diff"
• "git_remote_list"
• "git_worktree_list"
• "git_stash_list"
• "git_tag_list"
• "git_blame"
• "git_show"
• "git_branch_ahead_behind"
• "git_commit_create"
• "git_branch_create"
• "git_checkout"
• "git_merge"
• "git_stash_save"
• "git_stash_pop"

---

Git Operations Skill

Version: 1.0.0 Purpose: Git version control operations for repository management

---

Triggers

---

Integrated MCP Tools

This skill wraps the following MCP tools from miyabi-mcp-bundle:

---

Workflow

Phase 1: Repository Assessment

Step 1.1: Check Status

CopyUse git_status to see:
- Current branch
- Staged files
- Unstaged modifications
- Untracked files

Step 1.2: Review Recent History

CopyUse git_log with limit=10 to see recent commits

Phase 2: Change Review

Step 2.1: Unstaged Changes

CopyUse git_diff to see uncommitted changes

Step 2.2: Staged Changes

CopyUse git_staged_diff to review what will be committed

Phase 3: Commit Workflow

Step 3.1: Stage Files

Copygit add <files>

Step 3.2: Create Commit

CopyUse 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