What problem does it solve? Code reviews often miss breakage that lives outside the diff: downstream callers, wire formats, feature flags, and library behavior that grep cannot reveal. This Skill finds what a change could break somewhere else before it ships, and replaces confident-sounding writeups with proof obtained by running real code. ## Core Features & Use Cases - Hidden Breakage Detection: Looks where grep stops, including library source, pinned versions, JSON payloads, DB columns, wire formats, and code three hops downstream. - Proof-Based Verification: Identifies the single fact the change's safety depends on and proves it with a script or test that calls the real code, with an explicit confidence ladder from assertion to live reproduction. - Honest Risk Reporting: Separates confirmed risks with real file:line citations from checked-and-cleared cases, and marks anything unproven instead of rounding up. - Use Case: Before merging a small diff you do not trust, ask for its blast radius and receive the one safety fact either proven by a runnable script or explicitly marked unproven, plus the cheapest test to catch the real bug. ## Quick Start Ask the assistant to analyze the blast radius of your current diff and prove the key safety assumption by running the real code.
