What problem does it solve? Code reviews often miss issues because reviewers look at changes from a single angle, letting security flaws, architecture violations, or logic bugs slip through. This Skill structures review into five independent analysis perspectives with a shared severity model, producing a deduplicated, prioritized findings report. ## Core Features & Use Cases - Five Parallel Perspectives: Analyzes correctness, hexagonal architecture boundaries, security (OWASP, secret exposure), project conventions (Biome, test naming, InversifyJS), and CRAP complexity. - Severity Model with Anti-Inflation Rules: Classifies findings as Critical, High, Medium, or Low with strict criteria that prevent severity inflation. - Verification Before Reporting: Confirms findings via test suites, lint checks, and type checks so only verified issues are reported. - Use Case: When reviewing a pull request in a TypeScript hexagonal-architecture project, run all five perspectives on the diff, then receive a prioritized report with file:line evidence and fix directions. ## Quick Start Review the changes in this pull request using the five code review perspectives and report prioritized findings with severity levels.
