Git Manager.

The problem

LLMs often struggle with Git safety, accidentally nuking unstaged work, force-pushing over protected branches, or staging sensitive files via broad glob patterns. Manual Git management through an agent can be risky without a strict state machine to prevent destructive accidents.

What it does

• Enforces path-scoped staging and hunk reviews to prevent "git add ." accidents.
• Maintains protected trunk invariants by blocking direct commits to main/master.
• Validates repository identity and worktree state before every mutation.
• Verifies remote state via GitHub CLI (gh) rather than relying on local exit codes.
• Provides recovery plans for history-changing operations like interactive rebases and conflict resolution.

Frameworks & tools

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

Why this beats prompting it yourself

DIY prompting usually fails to account for Git's edge cases, like detached HEAD states or in-progress rebases. This skill treats Git as a formal state machine, requiring re-validation of HEAD and the index immediately before execution to ensure no "mid-air collisions" with your own manual work.

Use cases

• Safe feature branch management with automatic upstream synchronization.
• Interactive rebase and conflict resolution with pre-planned recovery steps.
• Compliant pull request creation and verification using GitHub CLI.
• Atomic staging of specific hunks while preserving unrelated local changes.

Known limitations

Requires standard git and gh binaries installed. Explicitly refuses to run repository-provided scripts, hooks, or custom aliases to maintain security boundaries.