code-review

# Code Review: Correctness Review the changed code for **correctness bugs** — cases where it does the wrong thing, crashes, corrupts state, or breaks a contract. This skill is deliberately scoped to bugs. Do not report reuse, quality, style, or efficiency cleanups here; those belong to a separate cleanup pass (San's `simplify` skill, where present). If the arguments include `--fix`, apply fixes after reporting. Otherwise report only and offer to fix. A leading focus area (e.g. `concurrency`) narrows the review to that dimension. ## Phase 1: Identify Changes Run `git diff` (or `git diff HEAD` when changes are staged) to see what changed. If there are no git changes, review the most recently modified files the user named or that you edited earlier in this conversation. Read enough of the surrounding code that each changed line can be judged in context — a line is rarely a bug on its own, only against the code that calls it and the code it calls. ## Phase 2: Launch Review Agents in Parallel Use the Agent tool to launch the dimension agents concurrently in a single message (foreground — do NOT set `run_in_background`). Pass each agent the full diff plus the context it needs. Each agent returns a list of findings; every finding must carry: - a **severity** — `critical` (crash, data loss, security), `high` (wrong result on a realistic input), `medium` (wrong only in an edge case), `low` (fragile, latent); - a **`file:line`** reference; - a **concrete failure scenario** —...