Ca Commit

arbiterforge/ca-commit

Run the full commit gate — the only sanctioned path to a git commit.

247 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

138

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/arbiterForge/codeArbiter --skill ca-commit

4 sections, as written by the author

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.

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.

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.

MUST NOT commit without commit-gate clearing. MUST NOT commit if the project test suite is not

green.

Copy the folder

Take arbiterforge/ca-commit from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.