Code Review

Review code against the style guide in references/style-guide.md. Produce a structured, severity-tagged findings report that a human can skim in 30 seconds and an agent can act on directly.

What gets reviewed

Default scope, in order of preference:

1. Explicit target — if the user names a file, PR, branch, or diff, review exactly that
2. Current branch vs main — git diff main...HEAD when reviewing "my changes" / "this branch"
3. Uncommitted changes — git diff HEAD + git diff --staged when reviewing "what I just wrote"
4. Ask — only if genuinely ambiguous. Don't ping-pong.

Skim the diff first, then read surrounding context for any file with non-trivial changes. A review that misses the calling context misses half the bugs.

Output format

Always use this structure. Omit sections that are empty — don't pad with "no issues found".