Commit Gate
A strict commit-discipline skill that lets nothing reach version control until nine blocking gates — from explicit authorization to a clean post-commit tree — are cleared.
Dev & CodingAdvanced★ 147⑂ 8AI score 8/10Last updated: Oct 3, 2026
What it does
When you run /commit or otherwise ask for staged changes to be persisted, this skill refuses to commit directly and instead walks nine blocking gates:
- Permission — "looks good" is not authorization; only an explicit commit instruction passes.
- Branch — stops on
main,master, or any protected branch. - Classification — forces the staged set into one type (
feat/fix/test/refactor/docs/chore/ci) and splits mixed sets. - Verification — runs test, lint/type-check and secrets-scan commands read from
tech-stack.md(never guessed), and routes crypto/secret, DB-migration and CI/deploy diffs to dedicated review gates. - Behavioral proof — reruns a fresh command, reads output and exit code, and matches it against the spec's acceptance criteria.
- Diff review — blocks unexpected files, credentials, TODO/stubs, disabled tests and scope creep.
- Selective stage — explicit paths only;
git add -A,git add .and wildcards are forbidden. - Message — Conventional Commits, ≤72-char subject, a WHY body,
CHANGELOG:footer for feat/fix. - Commit — non-interactive commit, new commit (never
--amend) after hook failure, then a SHA + gate report.
Who it's for
- Leads who want commit hygiene enforced rather than suggested.
- Teams that want to stop an AI agent from committing unverified work.
- Users of the codeArbiter plugin, or anyone building a similar gate pipeline.
Examples
/commitwith two failing tests → blocked at Phase 4 until fixed and re-run.- Feature code and docs staged together → Phase 3 splits them into separate
featanddocscommits. - A DB migration is staged → the H-14 hook blocks the commit until
migration-reviewerpasses and the content-bound marker is recorded.
· · · Install guide · · ·
Try it now, no install
Paste this into Claude to use the skill without installing anything.
Read the instructions in this file and follow them to help me: https://raw.githubusercontent.com/arbiterForge/codeArbiter/HEAD/core/surface/skills/commit-gate/SKILL.md What I want: (describe your task here)
If Claude can't open the link, open it yourself and paste the contents instead.
↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.
Install in the Claude app (no terminal)
- Download the ZIP with the button below.
- In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
- Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Install in Claude Code
Let Claude do it — paste this into Claude Code
Install the skill I found on Claude Skill Mart. Copy the core/surface/skills/commit-gate folder from the GitHub repo arbiterForge/codeArbiter into my ~/.claude/skills/commit-gate/. When it's done, tell me in one line what this skill can do.
Install with a command instead
git clone https://github.com/arbiterForge/codeArbiter.git && mkdir -p ~/.claude/skills && cp -r codeArbiter/core/surface/skills/commit-gate ~/.claude/skills/⚠ This is a third-party skill. Check the source repository before installing.
- Open a terminal and change into your working directory.
- Clone the repository:
git clone https://github.com/arbiterForge/codeArbiter.git - Create the skills directory:
mkdir -p ~/.claude/skills - Copy the skill:
cp -r codeArbiter/core/surface/skills/commit-gate ~/.claude/skills/ - This skill references the plugin's
includes/,hooks/andagents/files, so for full behavior install the whole repository as a plugin (see the repo README). - Create
.codearbiter/tech-stack.mdin your project root with your test, lint and secrets-scan commands — without it the skill stops at Phase 4. - Restart Claude Code, then try
/commitor "commit these changes" to confirm the gates run.
View source on GitHub ↗License: AGPL-3.0