commit-gate

Enforce a nine-phase commit workflow with tests, linting, and secrets scanning.

139|7|Updated May 8, 2026
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill commit-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit-gate
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/commit-gate
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill commit-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents unsafe or unverified commits from reaching version control by forcing staged changes through explicit authorization, branch safety checks, verification, proof, and diff review.

Core Features & Use Cases

  • Enforces a nine-phase commit workflow covering permission, branch validation, change classification, tests, linting, secrets scanning, behavioral proof, diff review, selective staging, and commit messaging.
  • Blocks common failure modes such as committing to protected branches, shipping red or unproven changes, or accidentally including secrets, migrations, or scope creep.
  • Use it when you need a disciplined, audit-friendly commit process that reports gate results and leaves the working tree clean.

Quick Start

Ask the Skill to review the staged changes and produce a commit-ready report for the current branch.

Frequently Asked Questions about commit-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent secrets and unproven changes from being committed to git?

To prevent secrets and unproven changes from being committed to git, you can enforce a multi-phase commit workflow that includes secrets scanning, behavioral proof verification, and lint checks before authorizing any staged changes.

What is a commit gating workflow and when do I need it for feature branches?

A commit gating workflow is an automated verification process that validates staged code changes against safety, testing, and review criteria before they reach version control. You need it for feature branches and release workflows requiring audit-friendly discipline.

How do I stop accidental commits to protected branches in my release workflow?

To stop accidental commits to protected branches in your release workflow, apply a commit gate that performs explicit branch validation and requires clean authorization before allowing any staged changes to proceed to the final commit.

Does commit gating work without external dependencies or testing frameworks?

Yes, commit gating operates without external dependencies, using internal logic to enforce branch checks, test verification, secrets scanning, behavioral proof, and diff review across nine distinct phases to ensure a clean git status.

What is the best way to automate lint verification and diff review before a commit?

The best way to automate lint verification and diff review before a commit is to route staged changes through an automated gating process that classifies changes, runs verification, generates behavioral proof, and enforces selective staging.

Why does my commit workflow leave the working tree dirty after a failed gate check?

A commit workflow may leave the working tree dirty after a failed gate check if it lacks a final clean git status enforcement step. A proper commit gate ensures the working tree remains clean even when verification fails.