Skip to content

Fast paths

The big picture: Every change falls into a class, and the class names the gates that run, in order. A typo fix runs one step; a full-stack feature runs the whole chain.

Why it matters: Running the heaviest chain on every change is the failure this table exists to prevent. Find your row, run what it names, and stop.

The table below is read from the repository’s CLAUDE.md when the site is built. It is the only copy: nothing here is retyped, so it cannot be out of date, and scripts/check-single-fastpath-table.sh fails CI if a second copy appears anywhere else.

Change classRequired gates (in order)
Pure bugfix with identified root cause/code-review (trial, see below) → regression-check → test-scaffold (if no coverage) → completeness-check → changelog-check → /mr
Dependency bump (single package, no API change)dependency → changelog-check → /mr
Docs-onlydocs (if a new page) → completeness-check → /mr
Chore / CI config / lint-only/mr
Schema / migration change only (no behavior change)schema-check (before push) → test-scaffold → completeness-check → changelog-check → /mr
Backend-only feature (new internal endpoint or model; an endpoint users call directly takes the *New user-visible feature* row)architect → pre-MR gate batch → test-scaffold → completeness-check → changelog-check → /mr
Wiring onto an already-designed surface (a form or toggle bound to an *existing* API contract, inside a shell whose design already shipped, no new interaction pattern)ux-review (visual diff) → rbac-check + security-review + regression-check → test-scaffold → completeness-check → changelog-check → /mr
Frontend-only feature (no API change)architect → ux-design → implement → ux-review + accessibility → test-scaffold → completeness-check → changelog-check → /mr
New user-visible feature (full stack)/voc → architect → ux-design → implement → pre-MR gate batch → ux-review + accessibility → test-scaffold → completeness-check → changelog-check → /mr
New trust-boundary subsystem (auth, uploads, tenancy, external input)threat-model → architect → implement → pre-MR gate batch (incl. security-review + rbac-check) → test-scaffold → completeness-check → changelog-check → /mr
  • When a change spans rows, take the union. When it is genuinely ambiguous, take the heavier row and say which one you chose and why.
  • A row names the gates that run by default. It never switches off a gate whose trigger is in the diff: security and access-control review whenever a view, route, handler, endpoint, serializer, permission or auth path changed, and performance review whenever a query or data-access path changed.
  • changelog-check is a script (make check-changelog), not an agent.
  • The change-class: line in an MR’s ## Gates section names the row you took (see The Gates ledger).
  • The rules around the table, such as the pre-MR gate batch and the gate-by-gate notes, are in CLAUDE.md itself. For the narrative version, see Development workflow.