Claude Skill MartBrowse skillsQuick linesLearn by videoTerminal guideWhat is a Skill?
Back to list

Commit Gate

Forces every commit through nine blocking gates — permission, branch, classification, test/lint/secrets, behavioral proof, diff review, selective staging, message, commit.

Dev & CodingAdvanced1418AI score 8/10Last updated: Aug 17, 2026

What it does

When you ask for /commit, this skill stops Claude from firing git commit and walks nine blocking gates instead:

  1. Permission — vague signals like "looks good" are explicitly NOT authorization
  2. Branch — halts on main, master, or any protected branch
  3. Classification — one type only (feat/fix/test/refactor/docs/chore/ci); mixed sets get split
  4. Verification — tests, lint, type-check and secret scan must all pass; crypto/secret/migration/CI changes get routed to dedicated reviewers
  5. Behavioral proof — run a fresh command, read output and exit code, match it against the spec's acceptance criteria
  6. Diff review — blocks unexpected files, credentials, TODOs/stubs, disabled tests, scope creep
  7. Selective staginggit add -A and git add . are forbidden; explicit paths only
  8. Message — Conventional Commits, subject ≤ 72 chars, a WHY body, CHANGELOG footer for feat/fix
  9. Commit — capture the SHA, verify a clean git status, never --amend after a hook failure

Who it's for

  • Developers and tech leads who want commit hygiene and atomic commits enforced, not suggested
  • Anyone worried about an agent mass-staging a repo or committing straight to main
  • codeArbiter plugin users, or people who want to port this rule set into their own workflow

Examples

  • Example 1: You say "go ahead and commit" → the skill sees you are on main, stops, and asks you to create a feature branch first.
  • Example 2: An API key slipped into a staged file → caught twice (secret scan plus diff review), the file is unstaged and the leak consequence is spelled out.
  • Example 3: Feature code and docs are staged together → split into separate feat and docs commits.

· · · 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)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
Download 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.

  1. Open a terminal.
  2. Clone the repo: git clone https://github.com/arbiterForge/codeArbiter.git
  3. Create the skills folder: mkdir -p ~/.claude/skills
  4. Copy the skill: cp -r codeArbiter/core/surface/skills/commit-gate ~/.claude/skills/
  5. This skill references codeArbiter hooks, agents and includes files — for the full behavior, install the whole plugin per the repo README.
  6. Add .codearbiter/tech-stack.md to your project listing the test, lint and secret-scan commands (without it the skill stops rather than guessing).
  7. Restart Claude Code and run /commit to confirm the gates trigger.
View source on GitHubLicense: AGPL-3.0