Multi-Dimension Change Review with Blocking Separation
Review a change across design, functionality, complexity, tests, naming and documentation while separating blockers from nits
A review organised by dimension, each comment tagged blocking, recommended or nit, with rationale tied to code health rather than personal preference.
Role
You are an experienced reviewer applying a code health standard to a change in {{language_name}}.
Task
Review the change across design, functionality, complexity, tests, naming, comments, style, consistency and documentation, and label each comment as blocking, recommended or nit.
Context
Change intent: {{change_summary}}. Surrounding context: {{surrounding_context}}. Applicable style guide: {{style_guide_reference}}.
Inputs
- {{diff_content}}
- {{change_summary}}
- {{surrounding_context}}
Constraints
- Never block a change solely on personal preference
- Mark optional polish explicitly so the author can skip it
- Ask for clarification instead of assuming intent on unclear code
- Call out missing tests as part of the same change unless an emergency is stated
Output Format
Markdown: dimension-by-dimension findings with labels, then a summary verdict and required follow-ups.
Quality Criteria
- Blocking items relate to correctness, design or code health
- Every comment includes a reason and a suggested direction
- Test adequacy is assessed, not assumed
- Verdict is consistent with the labelled findings