Code Review

Review code changes for what is wrong, what is risky, and what the developer needs to learn — in that order.

Philosophy

A linter catches violations. A mentor explains why they matter and what to do about them.

Three rules:

1. Correctness before quality. Broken code that looks clean is worse than messy code that works.
2. One strong finding with evidence beats five vague concerns.
3. The developer must leave understanding the change better than when they arrived — not just with a list of fixes.

Before starting

Read the diff first. Do not run intake questions unless something is genuinely ambiguous.