pre-push

Mechanical checklist that catches the reviewer / CI failures a repo has actually had, plus a spec-link check that enforces the SDD loop locally — before the PR is open, so the author sees the problem locally instead of hearing it from a reviewer or a pr-spec-sync bot.

This is the repo-agnostic half. Each consumer repo overlays its delta in its CLAUDE.md and its <repo>-dev-process sister skill:

• The check gate — the single command (or short sequence) that reproduces what CI runs: e.g. just check on one repo; RUSTFLAGS="-D warnings" cargo build/test/clippy + cargo fmt --check on another. Read the repo's CLAUDE.md or <repo>-dev-process for the exact gate and any diff-conditional extra gates (schema-drift, VD validation, seam lint, migration renumber, UI smoke).
• Repo-specific collision patterns — the high-churn files and the recurring logical conflicts (enum variants, event schema, migration numbering, generated fixtures). The generic patterns are below; the repo's CLAUDE.md / <repo>-dev-process names the rest.

When a new product surface lands, fold its gate into the repo's overlay — the checklist tracks the toolchain, it does not lag it.

Why

CI on pull_request checks out a merge of origin/main + the PR branch, not the branch alone — and often with strict warnings (-D warnings or equivalent). A local build without that merge, with default flags, is insufficient. Reproducing the merge preview locally is the whole point of step 1.

The spec-link step enforces "no PR without a spec or a trivial label" at push time, before the PR is open.

Steps