precommit

Pre-Commit Checks (Full)

Trigger

• Keywords: precommit, pre-commit, lint and test, quality gate

When NOT to Use

• Quick checks without build (use /precommit-fast)
• Verification loop without lint:fix (use /verify)
• Just running tests (run directly)

Workflow Steps

Step	Goal	Safety	Skip if Missing
comment_blocks	Reject over-long comment blocks (@rules/docs-writing.md § Code Comments)	read-only	yes
lint-fix	Auto-fix code style issues	read-write	yes
build	Verify compilation succeeds	read-only	yes
test-unit	Run full test suite	read-only	yes

Failure behavior: continue-all (run all steps, report all results)

comment_blocks is a policy step, and the asymmetry is deliberate (POLICY_STEPS in scripts/precommit-runner.js): it can FAIL the run, but it never counts as "validation ran". A run where policy was the only thing that executed still reports ⚠️ NO CHECKS RUN, so a repo whose real checks are pytest/cargo cannot bank a ✅ PASS on a passing comment scan alone. It runs first because it is static and cheap.

Task

Run pre-commit checks: lint:fix -> build -> test

Step 1: Check for runner script

Use Glob to check if .claude/scripts/precommit-runner.js exists in the project root.

• Found → run: node .claude/scripts/precommit-runner.js --mode full --tail 80
  • If runner emits ## Overall: ✅ PASS, use its output and skip to the Output section.
  • If runner emits ## Overall: ⚠️ NO CHECKS RUN, do NOT treat it as a pass — fall through to Step 2 ecosystem detection so the project's real checks run. The marker means no project validation executed and no policy step failed — every validation step was a skip or unavailable, and any policy step (comment_blocks) either skipped or passed (a FAILING policy step is ❌ FAIL, never this marker — line 30's asymmetry) — whether because the repo declares no runnable checks or because the required tools were not available to the runner (which orchestrates the ecosystem table below itself: it detects pyproject.toml/Cargo.toml/go.mod/… and runs those checks as first-class steps). The runner self-notes its own verdict (review-state.js note precommit pass|fail); on ⚠️ NO CHECKS RUN it notes nothing — the slot is untouched and the reminder persists, which is the correct reading of "nothing validated".
  • If runner fails (## Overall: ❌ FAIL), treat as a real precommit failure (do not silently fallback).
• NOT found → Auto-install attempt (see precommit-fast for identical auto-install logic), then fallback to Step 2.