commit

/evo:commit

Gated interactive commit. A commit only lands if simplify → review → lint → targeted-test all pass; the gate writes .commit-gate/attestation.json bound to sha256(git diff HEAD). The commit goes through evolve ship --class manual, which hard-verifies that attestation at this repo's real commit chokepoint — ship-gate forbids bare git commit, and ship commits internally, so this Go-side check (go/internal/phases/ship/commitgate.go) is the single enforcement point. This skill is the intelligent driver — the gate itself is evolve commit-gate run (Go; go/internal/commitgate/).

Procedure

Follow in order. Do not edit any file between step 4 and step 5 — that would make the attestation stale and ship will refuse.

1. Stage everything: git add -A. The sanctioned commit path (evolve ship --class manual) commits the whole working tree, so this is an all-or-nothing commit (not a partial one). Staging now also lets new files be reviewed and bound into the attestation.

2. Detect changed languages: git diff --name-only HEAD, then map extensions (.go→go, .py→python, .ts/.tsx/.js/.jsx→ts, .rs→rust).

3. Review chain — invoke via the Agent tool on the staged diff. Apply every CRITICAL/HIGH finding, re-stage (git add -A), and re-run until clean. Record the names you actually ran. Two reviewers are required, except for a proven comment removal and a docs-only change (see the contract below). A docs-only change, where every changed path ends in .md, runs the docs-review skill instead:

   #	Agent (or skill)	Covers
   a	simplify: code-simplifier (or ecc:code-simplifier)	clarity, dead code, simplification
   b	one review: the matching language reviewer (go-reviewer / python-reviewer / typescript-reviewer / rust-reviewer) OR the general code-reviewer / /code-review — pick one	correctness, security, semantics

   Prefer the language reviewer when there's a clear primary language (richer); use the general code-reviewer for mixed/other languages. The combined evo:code-review-simplify skill satisfies both a and b in a single pass.

4. Scan for secrets, then run the gate: first "$CLAUDE_PROJECT_DIR/go/bin/evolve" scan secrets --staged, then "$CLAUDE_PROJECT_DIR/go/bin/evolve" commit-gate run --reviewers "<comma-list of what you ran>".

   • The scan is read-only and deterministic: it checks the staged diff's added lines and prints each finding as <file>:<line>: <rule>: <masked match> (raw secrets are never printed). exit 0 → run the gate; exit 1 → remove the secret, re-stage, return to step 3; exit 2 → git failed (not a repo, bad revision); stop and report.
   • This is the gate (Go; go/internal/commitgate/): lang-detect, the --reviewers precondition, the lint lanes, and the tree-SHA-bound attestation. (The original bash runner was deleted once a differential-parity test proved the two byte-identical; a Go-only golden test now pins the attestation byte layout.)
   • exit 0 → attestation written; proceed immediately to step 5 (no edits in between).
   • exit 1 → reviewer-precondition or lint/test failure, or nothing staged (read stderr). Fix, re-stage, return to step 3 for the affected files.
   • exit 2 → git/SHA fatal (not a repo, git diff HEAD failed). Stop and report.
   • exit 3 → a required tool is missing/could not be installed; surface the printed manual install command to the user and stop.

5. Commit + push via the sanctioned path (handles both, on the current branch):

   "$CLAUDE_PROJECT_DIR/go/bin/evolve" ship --class manual "<message>"
   

   • --class manual re-stages (git add -A, a no-op after step 1), verifies the commit-gate attestation matches the staged tree (the Go-side hard gate), commits to the current branch, and pushes origin/<branch>.
   • Non-TTY agents (LLM invocations): the command will fail with a non-TTY error that includes the exact IPC auto-confirm env var to set. Set it before re-running. The signal name comes from envShipAutoConfirm in go/internal/phases/ship/verify.go.
   • If it refuses with "stale" or "missing … attestation" → a file changed after step 4; return to step 3.

6. Watch CI (skip with a clear note if gh is absent or the repo has no workflows):

   • evolve ci watch --sha "$(git rev-parse HEAD)" on main (a red files one fix-forward inbox item), or evolve ci watch --pr <n> on a PR branch (files nothing). Exit 0 = green, 1 = red (the output carries the ci classify verdict), 2 = the run could not be observed (gh failure or the ci_watch.timeout_s policy timeout).
   • green → done; report the run URL.
   • red → perform one auto-fix pass: read the printed classify table (or gh run view --log-failed) → fix → repeat steps 1–5 as a new commit (never force-push). Re-watch once. If still red, stop and report the failing job + logs for the user to decide.