How to give and receive code reviews that actually ship better software.
Tip: Log in to save your checklist progress across devices.
Aim for < 400 lines. Larger PRs miss bugs and stall.
Comment on changes, not the person. Be kind and specific.
Does it do what the description says? Edge cases, error paths, race conditions.
Is the abstraction right? Is it readable in 6 months?
Are there tests? Do they cover the new behavior + a regression case?
For UX/perf/security work, don't just read — try it.
Security, perf, a11y, observability — make it explicit.
"What do you think about X?" beats "Change this."
Distinguish nits, suggestions, and blockers in your comments.
A 24-hour response SLA keeps team velocity high.