/code-review
ReviewModel-invoked
Three-axis review from a fixed git point — parallel subagents, findings tagged blocker / suggestion / nit.
When to use
Before merge, or when asked to review a branch, PR, or diff — including cuts for over-engineering.
Prerequisites
- A branch or diff with a clear git baseline (e.g. `main`).
- Implementation for the slice is largely done (/dev).
How to use
- Invoke /code-review and pin the baseline (e.g. review since `main`).
- Let the three axes run — Standards, Spec (if provided), Simplify.
- Triage findings: fix blockers, consider suggestions, defer nits as needed.
- Re-run or merge when blockers are clear.
Done when
Findings are listed with severity and blockers are resolved or explicitly accepted before merge.
Pipeline
- Upstream
- /dev
- Downstream
- Ship
Boundaries
Not lint-only or generic PR comments — always uses a pinned baseline. Spec is optional; Simplify always runs.
Tips
- Always pin a baseline — “review this PR” without a base is not enough.
- Long reviews: ask to use the `techlead` agent.
Sample prompt
prompt
/code-review Diff since main
Agent
PRINCIPAL TECH LEAD
Owns: Standards, Spec, Simplify, pre-merge gate
Use the techlead to review diff since main