Code Review

Review Order

Always review in this order to catch the most critical issues first:

1. Correctness — Does it do what it's supposed to?
2. Security — Does it introduce vulnerabilities?
3. Performance — Are there obvious bottlenecks?
4. Maintainability — Is it readable and well-structured?
5. Tests — Is the change adequately tested?

Correctness Checklist

• Logic matches the stated requirements
• Edge cases handled (empty input, nulls, boundary values)
• Error paths are handled, not silently swallowed
• No off-by-one errors in loops/slices
• Async code awaited correctly, no race conditions
• State mutations are intentional and isolated