Git Manager.

The problem

Coding agents commit straight to main, force-push over a protected branch, or run git add . and sweep a .env file in with everything else. None of that is hypothetical. It's what happens when an agent handles Git without something checking what it's about to do before it does it.

What it does

• Path-scoped staging with hunk review, so git add . accidents can't happen.
• Blocks direct commits to main/master, so protected trunk stays protected.
• Checks repository identity and worktree state before every mutation, not just once at the start.
• Confirms remote state through the GitHub CLI (gh) instead of trusting a local exit code.
• Gives you a disclosed recovery plan before history-changing operations like interactive rebase or conflict resolution, not after something's already gone sideways.

Frameworks & tools

Standard git and gh (GitHub CLI). Built for CLI-integrated environments like Claude Code or Cursor.

Why this beats prompting it yourself

Telling an agent to "be careful with git" doesn't cover the edge cases: detached HEAD, a rebase already in progress, a branch that moved since the plan was made. This skill re-checks HEAD and the index immediately before executing, so a plan from a few messages ago can't collide with changes you made in between.

Use cases

• Feature branch work that won't quietly touch main.
• Interactive rebase and conflict resolution with a recovery step already planned out.
• Pull requests that get verified against GitHub's actual state before they're reported done.
• Staging exactly the hunks you meant to, without dragging in unrelated local changes.

Known limitations

Needs standard git and gh binaries installed. Won't run repository-provided scripts, hooks, or custom aliases. That boundary is intentional, not a gap.