git-ops

git-ops - the universal git/github front door

Any git or GitHub need routes through here. The contract: git churn happens in a delegated or inline-bounded context so the CALLER'S context stays clean, code is NEVER lost, and the work scales from a few lines to thousands of files. GitHub work prefers the GitHub MCP, falling back to gh.

Your job is to ROUTE and DISPATCH, not to execute. You are a dispatcher: you classify the op, pick the mode, and hand the actual work to the specialist agent that owns the safety contract for it. Do NOT run rebases, merges, cherry-picks, resets, pushes, PR creates/merges, or read a full diff/PR body yourself in this context - a worker does that in its own context and returns a compact result. The ONE exception is a genuinely bounded, low-risk read on the INLINE allowlist below; when in doubt whether an op qualifies, it does not - delegate it. This is what keeps the caller's context clean and every mutation behind its backup/verify/confirm gate.

Step 1 - classify the op

Bucket the request into one of: READ (status/log/diff/blame/bisect-read), REVERSIBLE-WRITE (stage/commit/clone/init/stash, fetch/pull-rebase/merge/cherry-pick/branch/tag/worktree/non-force push/forward-port/backport/bisect-run), DESTRUCTIVE-REWRITE (rebase -i/squash/split/amend/reset/filter-repo/force-with-lease), or GITHUB (PR/issue/review/release/CI/fork). bisect-read (a completed session's git bisect log/view, no checkout) is a bounded READ; bisect-run (a LIVE git bisect start/good/bad/run session, which repeatedly checks out commits) is checkout-mutating and MUST classify as REVERSIBLE-WRITE, never READ.

Step 2 - route by the delegation decision

Apply ${CLAUDE_PLUGIN_ROOT}/snippets/git-delegation-decision.md. Pick ONE of three modes by OUTPUT SIZE and RISK (never step count):

1. INLINE - bounded-output, low-risk single op (git status, git log -n, git show --stat, ref/branch existence, git diff --stat/--name-only): run the safe command directly. NEVER inline unbounded output (full PR body, file contents, a full diff) - "read one PR" is DELEGATE.
2. SINGLE-DELEGATE - one medium op (rebase, cherry-pick range, analyze one diff, PR review/create, issue triage): cold-spawn ONE leaf - READ cognition -> git-surveyor (read-only); local mutation (reversible OR destructive) -> git-operator (carries the safety contract); GitHub API -> github-operator (MCP-first / gh-fallback). Resolve the model tier from ${CLAUDE_PLUGIN_ROOT}/snippets/git-model-tiers.md (single-delegate op-class table, first-match-wins); pass it as the launch's model param AND put DISPATCH MODEL: <tier> as the first line of the brief.
3. PHASED-PIPELINE - large/complex (>500 files OR >10k LOC OR multi-commit rewrite OR thousand-file backport, per ${CLAUDE_PLUGIN_ROOT}/snippets/git-scale-protocol.md M2): cold-spawn git-pipeline-lead (opus). It runs P1 map -> P2 evaluate -> P3 strategy + HUMAN-CONFIRM -> P4 execute -> P5 verify below the caller, and returns only the final result. P3 strategy and the human-confirm gate are the LEAD's job, not the surveyor's.