What problem does it solve? Implemented changes often ship without independent scrutiny, letting defects in complex, cross-module, or high-risk code slip through. This Skill defines when review adds real evidence, how to construct a review request with the actual diff and verification context, and how to interpret and rerun reviews without ceremony. ## Core Features & Use Cases - Risk-Driven Review Triggers: Requests review only when complexity, security, data-loss, compatibility, or release risk justifies independent scrutiny, avoiding review as mere ceremony. - Structured Review Requests: Supplies the reviewer with the current working-tree diff or committed range, acceptance criteria, verification evidence, and constraints instead of prose summaries or transcripts. - Reviewer Lane Selection: Chooses between primary Reviewer profiles and Oracle cross-check lanes based on the evidence needed, with rules for interpreting findings and rerunning only after substantive changes. - Use Case: After implementing a cross-module API migration, dispatch a reviewer with the full diff, acceptance criteria, and test evidence to catch integration defects before merge. ## Quick Start Ask the agent to request an independent code review of the current working-tree changes against the acceptance criteria and test evidence.
