What problem does it solve? Code reviews often treat every changed line equally, so a 3-line change to a shared auth check gets the same attention as a 200-line change to a leaf component. This Skill ranks changed units by blast radius and checks whether the riskiest ones are actually covered by tests, answering "is this safe to merge" rather than "does this follow style". ## Core Features & Use Cases - Blast-radius ranking: Orders changed units by callers, callees, and affected execution paths instead of diff size, flagging changes on critical paths like auth, payments, data writes, and public APIs. - Targeted test verification: Checks coverage only for high-risk units, running the project's own test command and confirming the relevant test would fail if the change were reverted. - Risk-tiered report: Groups findings into high, medium, and low tiers with a merge recommendation, and names the specific missing test case for every untested high-risk unit. - Use Case: Before merging a pull request that touches a shared validation module and two UI components, run this Skill to learn that the validation change has callers on the payment path but no covering test, and get the exact missing test case to add. ## Quick Start Review the changes in this pull request against the main branch, rank them by blast radius, and tell me whether the riskiest units are covered by tests.
