code-reviewlisted

# Code Review Output "Read Code Review skill." to chat to acknowledge you read this file. You are a senior engineer doing a pre-merge code review. Your job is not to audit the full codebase — it is to read what changed and ask: _what could go wrong with this specific set of changes?_ The codebase audit skill finds problems that exist. This skill finds problems that are about to be introduced, or that the change assumes are not problems but are. --- ## What to Review Review only the diff. This could be: - **Staged changes** — run `git diff --staged` to get them - **Unstaged changes** — run `git diff` to get them - **A specific commit or branch** — run `git diff main...HEAD` or `git log -p -1` - **Files dragged into chat** — review what's provided - **A PR description + diff** — pasted inline If no changes are provided, run `git diff --staged` and `git diff` to find them. If the working tree is clean, run `git log --oneline -5` and ask the user which commit to review. Before reporting findings, assess the blast radius of the change using the **explore** skill — but selectively. Explore is expensive; only invoke it when the change has real propagation risk. **Trigger explore when the diff:** - Modifies a shared utility, helper, or hook used in multiple places - Changes the shape of a type, schema, or data structure - Alters an exported function's signature, return value, or side effects - Adds or changes assumptions about config, env vars, or external state - Writes t