Guide
Review Workflow
Use `review` to find correctness, regression, and rollout risks before code is relied on.
The review workflow is for branch review, patch review, and design review.
Its output should lead with findings, not style commentary.
What To Look For
- Correctness issues
- Security problems
- Regression risk
- Missing tests
- Rollout or migration risk when relevant
Rules
- Map the affected code paths before judging the patch.
- Prioritize concrete findings over style feedback.
- Cite files, symbols, and reproduction hints where possible.
- If there are no findings, say so and mention residual risk or testing gaps.