What problem does it solve? It prevents committing unverified code by enforcing a rule that a diff that merely looks correct is not evidence — the project's tests, typecheck, lint, and format checks must actually run and pass before any commit or push happens. ## Core Features & Use Cases - Pre-commit verification gate: Discovers the project's real check commands from the Makefile, package.json, pyproject.toml, or CI workflow and runs tests, typecheck, lint, and format checks in order, committing only when all are green. - Lint vs format distinction: Treats linting (ruff check, eslint) and formatting (ruff format --check, prettier --check, gofmt -l) as separate checks, since a passing linter does not imply a passing formatter. - Hook bypass prevention: Forbids --no-verify, --force, and admin-merge to push a commit through a failing pre-commit hook, and counters common rationalizations like "the subagent said it passed" or "I'll fix CI if it's red". - Use Case: After a subagent or previous session edited code and claims tests pass, run the full gate yourself on the current checkout before committing, rather than trusting the secondhand report. ## Quick Start Before committing my staged changes, run the project's full test, typecheck, lint, and format gate and only commit if everything passes green.
