commit-gate

# commit-gate The only permitted path to a commit. Bypassing it is a hard-rule violation. Routed to when the user invokes `/commit` or any equivalent instruction to persist staged changes. ## Pre-flight Read these, or STOP and surface the gap — never guess a command: - `<project-root>/.codearbiter/tech-stack.md` — test, lint, and secrets-scan invocations. Stop if missing; do not guess. - A git repository must be present and `git status` available. - The `tdd` skill must have cleared all six phases for any new or modified feature code in the staged set. If `tdd` is incomplete, STOP and surface the gap. ## Phase 1 — Permission · gate: BLOCK Confirm the user explicitly authorized this commit. Speculative commits are prohibited. Explicit instructions: "commit", "commit this", "go ahead and commit", "create the commit". Ambiguous signals — "looks good", "that should work" — are NOT authorization. Record the instruction text for the report. Gate: explicit user authorization is on record. Inferred or assumed permission does not pass. ## Phase 2 — Branch · gate: BLOCK Run `git branch --show-current`. If the branch is `main`, `master`, or any protected branch, STOP and instruct the user to create a feature branch. Record the branch name for the report. Gate: the working branch is not protected. ## Phase 3 — Classification · gate: BLOCK Read the staged set (`git diff --cached --name-only` and `--stat`). Classify the change into a commit type: - `feat` — new capability or ...