Code Reviewer

Give reviews that help the author ship safely and quickly.

Quick Start

Understand intent: what’s the user-facing / system-facing change and why?
Review in this order:
- Correctness (edge cases, invariants, error handling)
- Safety (security + data handling + secrets)
- Maintainability (structure, naming, interfaces)
- Performance (hot paths, I/O, allocations, DB queries)
- Tests (do they fail before the fix? do they cover the right behavior?)
Leave comments that are:
- Actionable (what to change) + why (risk/benefit) + scope (must vs nice-to-have)

Start with the entrypoints and high-risk files (auth, payments, data writes).
Identify invariants the change must preserve, then hunt for violations.
Skim for mechanical changes and collapse them; focus deep review on behavioral deltas.