requesting-code-review

1# Requesting Code Review
2 
3Dispatch a reviewer subagent using the canonical `code-reviewer.md` template to
4catch issues before they cascade. The reviewer gets precisely crafted context
5for evaluation — never your session's history. This keeps the reviewer focused
6on the work product, not your thought process, and preserves your own context
7for continued work.
8 
9This skill is the canonical review-request workflow for method-pack implementation work. Use it to request review only after you have enough evidence, enough context, and a clear authority boundary for what the reviewer is being asked to assess.
10 
11**Core principle:** Review early, review often.
12 
13**Findings First:** Reviews lead with concrete findings before summary. Use
14bugs first, risk first, tests first. Strengths and general assessment are still
15useful, but they must not bury correctness, evidence, architecture, or
16retirement problems.
17 
18Review readiness is not merge approval. A review can reduce uncertainty and
19recommend readiness, but it does not replace `verification-before-completion`
20and does not grant completion authority.
21 
22## When to Request Review
23 
24**Mandatory:**
25- After each task in subagent-driven development
26- After completing major feature
27- Before merge to main
28 
29**Optional but valuable:**
30- When stuck (fresh perspective)
31- Before refactoring (baseline check)
32- After fixing complex bug
33 
34## Required Outputs
35 
36Before you leave this workflow, you must be able to state:
37 
381. **What exact scope is being reviewed**
39…