commit-gate
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, commit. Nothing reaches version control without clearing every gate; "it looks good" is not authorization.
npx skills add arbiterForge/codeArbiter --skill commit-gate --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# commit-gate The only permitted path to a commit. Bypassing it is a hard-rule violation. Routed to when the user invokes `/commit` or any equivalent instruction to persist staged changes. ## Pre-flight Read these, or STOP and surface the gap — never guess a command: - `{{PROJECT_DIR}}/.codearbiter/tech-stack.md` — test, lint, and secrets-scan invocations. Stop if missing; do not guess. - A git repository must be present and `git status` available. - The `tdd` skill must have cleared all six phases for any new or modified feature code in the staged set. If `tdd` is incomplete, STOP and surface the gap. ## Phase 1 — Permission · gate: BLOCK Confirm the user explicitly authorized this commit. Speculative commits are prohibited. Explicit instructions: "commit", "commit this", "go ahead and commit", "create the commit". Ambiguous signals — "looks good", "that should work" — are NOT authorization. Record the instruction text for the report. Gate: explicit user authorization is on record. Inferred or assumed permission does not pass. ## Phase 2 — Branch · gate: BLOCK Run `git branch --show-current`. If the branch is `main`, `master`, or any protected branch, STOP and instruct the user to
- Pre-flight
- Phase 1 — Permission · gate: BLOCK
- Phase 2 — Branch · gate: BLOCK
- Phase 3 — Classification · gate: BLOCK
- Phase 4 — Verification · gate: BLOCK
- Phase 5 — Behavioral proof · gate: BLOCK
- Phase 5.5 — Provenance auto-heal (conditional)
- Phase 6 — Diff review · gate: BLOCK
- Phase 7 — Selective stage · gate: BLOCK
- Phase 8 — Message · gate: BLOCK
- Phase 9 — Commit · gate: BLOCK
- Hard rules
What does the commit-gate skill do?
The only path to a commit. Routed to when the user invokes /commit or otherwise instructs codeArbiter to persist staged changes. Nine gated phases — permission, branch, classification, verification (test/lint/secrets), behavioral proof, diff review, selective stage, message, commit. Nothing reaches version control without clearing every gate; "it looks good" is not authorization.
How do I install it?
Run `npx skills add arbiterForge/codeArbiter --skill commit-gate --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arbiterForge/codeArbiter, a repository with 138 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.