Blast radius Find what a change breaks somewhere else, before it ships. Use for "blast radius of X", "what could this break", or reviewing a small diff you don't trust yet. Companion to how and why . how tells you what the code does. why tells you why it's shaped that way. Blast radius tells you what it breaks somewhere else. Listing the callers is not the job. The agent can grep those in a second. The job is the breakage grep won't show you. Don't trust your own writeup A blast-radius writeup that sounds right is worthless. It reads as convincing whether or not it's true, and that is the trap you are walking into. So don't hand back the writeup. Find the one or two facts the whole thing depends on and prove them by running code. Words are where you start, not what you ship. How sure are you For each fact the change's safety depends on, get it as far down this list as is cheap, and say where it stopped. Show more Installs 910 Repository cursor/plugins GitHub Stars 3.1K First Seen Jun 17, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass
blast-radius
安装
npx skills add https://github.com/cursor/plugins --skill blast-radius