Before merge, or when asked to review a branch, PR, or diff — including cuts for over-engineering.

• A branch or diff with a clear git baseline (e.g. `main`).
• Implementation for the slice is largely done (/dev).

1. Invoke /code-review and pin the baseline (e.g. review since `main`).
2. Let the three axes run — Standards, Spec (if provided), Simplify.
3. Triage findings: fix blockers, consider suggestions, defer nits as needed.
4. Re-run or merge when blockers are clear.

Findings are listed with severity and blockers are resolved or explicitly accepted before merge.

Upstream

/dev

Downstream

Ship

Not lint-only or generic PR comments — always uses a pinned baseline. Spec is optional; Simplify always runs.

• Always pin a baseline — “review this PR” without a base is not enough.
• Long reviews: ask to use the `techlead` agent.