PR Review Workflow
Goal
Find the highest-impact issues in the change. The output is for an engineer deciding whether the PR can merge.
Process
- Read the diff and the surrounding code needed to understand behavior.
- Identify changed contracts, data flow, error handling, user-visible behavior, and tests.
- List findings first, ordered by severity.
- Keep summaries brief.
Finding Rules
- A finding must describe a concrete risk.
- A finding must include file and line evidence.
- Do not include speculative issues without stating the assumption.
- Do not include style-only comments.
- If there are no issues, say that clearly and mention residual test risk.
Output Format
Use templates/review-output.md.
Verification
Before finishing, apply verification.md.