What problem does it solve? Code review is inconsistent: reviewers miss edge cases, flag style nits while ignoring broken invariants, or mix finding with fixing. This Skill provides a disciplined two-mode review process that checks spec compliance, correctness, and quality in a fixed order, and a codebase sweep that files findings as tasks without losing breadth. ## Core Features & Use Cases - Diff Review: Pins a comparison point (commit, branch, or files), reads whole files rather than hunks, and evaluates changes across three ordered axes: spec compliance, correctness (invariants, callers, error paths), and quality (complexity, patterns, naming). - Codebase Sweep: Breadth-first pass over all source files that finds duplication, anti-patterns, dead code, structural issues, and type-safety gaps, filing one task per finding group without proposing fixes. - Verified Findings Only: Requires confirming each claim by reading callers or reproducing the issue before flagging it; unconfirmed suspicions are raised as questions, not findings. - Use Case: After implementing a feature branch, run a diff review against main to catch a deleted validation check whose invariant is no longer re-established, with the exact file, line, and failure scenario named. ## Quick Start Review the diff of my current branch against main and report any spec, correctness, or quality findings with file and line references.
