Local Review

• IS: read-only review of a local diff, branch diff, or PR. Returns severity-tiered findings; leaves the working tree unchanged.
• IS NOT: fixing code (tidy), creating PRs (pr-creator), monitoring CI or review threads (pr-babysitter), frontend UX, accessibility, or rendered-quality review (ui-design Audit mode), library or CLI ergonomics (dx-audit), architecture briefs (codebase-architecture), reviewing plans (planning).

Only report issues you can defend with file:line evidence.

When to run: on the requested diff, including a failing one. Existing check results at the same revision are usable evidence; run a focused check when it can settle a finding, and report coverage limits.

Then hand off. tidy runs next in the usual flow, hunting complexity and applying what it finds, including this report's confirmed findings. So write the report to be consumed: every Fix: line has to be something a person could commit. Do not apply anything yourself, even a one-character fix; the moment this skill edits a file the user loses the read-only report they asked for.

Harness precedence

Claude Code bundles /code-review (correctness plus cleanups, with effort levels, --fix, and --comment) and /security-review (security on the current diff). A typed slash command runs the bundled skill, not this one; this skill runs when named or when a mode phrase below matches. It does not replace them. It adds Structural and Deslop modes, a whole-repo Security audit, a plausible tier the bundled commands filter out, REVIEW.md support (which the local /code-review does not read), and the same report on any harness, with git and the file tools alone. Do not run both on one diff unprompted; where a bundled review already ran this session, its findings enter the verdict step as candidates rather than being re-derived. Never reach for --fix or tidy mid-review to "confirm" a finding; that edits the tree the report is about.

Mode dispatch

Pick one mode from the user's wording; load only its references: