Code Review Request
Purpose
Summarize changes and request focused review with clear findings and an actionable fix plan.
When to Use
- •After quality pipeline passes in
/lazy task-exec - •Before commit or before
/lazy story-review
Behavior
- •Summarize: files changed, purpose, risks (≤5 bullets).
- •Table rubric: Issue | Severity (Critical/Warning/Suggestion) | File:Line | Fix Plan.
- •Patch plan: 3–6 concrete steps grouped by severity.
- •Optional: produce a PR-ready comment block.
Output Style
- •
table-basedfor findings; short bullets for summary and steps.
Guardrails
- •No auto-commits; propose diffs only.
- •Separate criticals from suggestions.
Integration
- •Coder/Reviewer agents;
/lazy task-execbefore commit;/lazy story-reviewpre-PR.
Example Prompt
Request review for changes in
src/payments/processor.pyand tests.