Code Review
Structured Code Review
Updated
A repeatable checklist for reviewing code changes.
- code-review
- quality
- process
Content
Review in passes: first correctness (does it do what it claims), then edge cases (empty input, overflow, concurrency), then readability (names, structure, comments that explain why), then tests (coverage of the new behavior and the failure paths). Comment on the change, not the author. Suggest concrete fixes, not just problems. Approve only when you understand the change well enough to explain it back.