What problem does it solve? Reviewing pull requests and diffs consistently is hard: reviewers miss security issues, skip tests, or give vague feedback. This Skill enforces a structured review process with explicit severity labels so every change gets checked against the same dimensions and produces an actionable summary. ## Core Features & Use Cases - Severity-labeled findings: Classifies every issue as blocking, important, nit, suggestion, or praise so authors know exactly what must be fixed before merge. - Multi-dimensional review: Checks correctness, simplicity, security, performance, error handling, testing, architecture, and whether every changed line traces to the stated goal. - Automated check integration: Runs the project's typechecker, linter, and tests, reporting failures as blocking issues. - Use Case: After finishing a feature branch, ask for a review of the diff against main and receive a verdict (Approve / Request Changes / Comment) with file-and-line-specific findings grouped by severity. ## Quick Start Review the changes on my current branch against main and give me a severity-labeled summary with a merge verdict.
