Code Review

Goal: find the issues that actually matter, ranked by impact, with concrete fixes. Not a style lecture.

1. Establish scope

Figure out what to review, in this order:

1. Files/snippets the user pointed at.
2. Otherwise git diff --staged; if empty, git diff; if empty, git diff main...HEAD (try master if main doesn't exist).
3. If still nothing, ask.

Run scripts/collect_diff.sh to get the diff plus a file list in one go. Read the surrounding code of every changed hunk — bugs usually live at the boundary between new and old code, so the diff alone is not enough.

2. Understand intent before judging

Read the commit message / PR description / user's explanation. Ask yourself: what is this change trying to do? A review that misses the intent produces noise.

3. Check, in priority order