What problem does it solve? After executing code changes, teams need a disciplined, evidence-based check before marking work done or opening a PR. This Skill enforces a hard review contract that compares the diff and EXECUTION.md against PLAN.md and TASKS.md, producing a structured REVIEW.md instead of ad-hoc gut checks. ## Core Features & Use Cases - Evidence-based findings: Every finding requires severity, location, evidence, impact, and recommendation — no vague claims allowed. - Requirement coverage check: Maps each requirement or task to evidence showing whether the change actually covers it. - Security and risk gates: Forces explicit checks when changes touch auth, permissions, secrets, files, network, or databases, and blocks a Ready verdict while artifact validators fail. - Use Case: After finishing a feature branch, run the review to get a REVIEW.md with findings by severity, testing gaps, residual risks, and a clear Ready / Needs fix / Blocked recommendation before opening the PR. ## Quick Start Use the review skill to evaluate the current diff against PLAN.md and EXECUTION.md and produce a REVIEW.md with findings and a readiness recommendation.