What problem does it solve? Code changes often get merged without independent verification, letting bugs, plan deviations, and missing tests cascade into later work. This Skill structures the review request so a fresh reviewer subagent evaluates the exact git range against the original requirements. ## Core Features & Use Cases - Structured Review Dispatch: Fills a code-reviewer prompt template with repository ID, checkout path, base/HEAD SHAs, snapshot tree, and test report so the reviewer gets precise context instead of session history. - Severity-Calibrated Feedback: Returns strengths plus issues categorized as Critical, Important, or Minor, with file:line references and a clear merge readiness verdict. - Verification Safeguards: Treats missing or mismatched evidence as Not verified, forbids inferring passing tests from code inspection, and keeps the review read-only on the checkout. - Use Case: After finishing a task in subagent-driven development, capture the base and HEAD commits, dispatch the reviewer subagent with the plan reference, fix Critical and Important findings, then proceed to the next task. ## Quick Start Ask the agent to request a code review of the changes between the recorded base commit and HEAD using the code-reviewer template before merging.
