/ca-commit
Run the full commit gate — the only sanctioned path to a git commit.
$ npx -y skills add arbiterForge/codeArbiter --skill ca-commit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ca-commit
Context preview
The summary Claude sees to decide when to auto-load this skill.
Run the full commit gate — the only sanctioned path to a git commit.
SKILL.md
ca-commit.SKILL.mdname: ca-commit description: Run the full commit gate — the only sanctioned path to a git commit. argument-hint: (none)
$ca-commit — commit gate
The only path to a commit. The orchestrator issues no `git commit` without the `commit-gate` skill clearing first. "It looks good" is not authorization. No arguments — the skill reads current git state (staged files, diff, test results) and decides whether every gate is green.
Routes to
The `commit-gate` skill (`${CLAUDE_PLUGIN_ROOT}/routines/commit-gate/SKILL.md`) — all phases. The skill is canonical for its phases, gates, and output format.
When NOT to use
- Before writing code → `$ca-feature` or `$ca-fix` first.
- To check PR readiness → `$ca-pr` (dispatches additional BLOCK-level reviewers).
- To run tests without committing → run the test command from `tech-stack.md` directly.
Hard gate
MUST NOT commit without `commit-gate` clearing. MUST NOT commit if the project test suite is not green.
When you can't trust yourself with your code base, trust Arbiter.
Repo: arbiterForge/codeArbiter
Other skills on codearbiter.
- /brainstorming
The Socratic spec-refinement front of /feature, and the planning front of /sprint. Routed to BEFORE any code — it takes a one-line idea and drives it to an approved, concrete spec with testable acceptance criteria. Four gated phases — frame, refine, write, approve. No
Open skill - /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,
Open skill - /context-check
Optional manual drift audit — report stale provenance-tracked docs (via _provenancelib drift detection across .codearbiter/.provenance/), then per stale doc offer re-scout / re-baseline / defer. Not the daily loop; commit-gate auto-heal owns routine maintenance.
Open skill - /context-creation
The brownfield back-fill. Routed to by /create-context, and by startup when .codearbiter/CONTEXT.md lacks the <!--INITIALIZED--> body marker but source code exists. Six gated phases — pre-flight, scout dispatch, synthesis, gap interview, write, lock. Reads the existing codebase
Open skill - /crypto-compliance
The banned-primitive gate. Routed to when changed code hashes, signs, encrypts, derives keys, generates security-relevant randomness, configures TLS, or imports a crypto library. Rejects broken primitives, disabled TLS verification, and home-rolled crypto; the approved-primitive
Open skill - /debug
Investigate-then-decide root-cause analysis for a defect whose cause is unknown (distinct from /fix, which assumes a known bug). Five gated phases: capture, hypothesize, gather, decide, hand off. Investigation only, no code changes; exits to /fix, /adr, or a no-action close.
Open skill

