- name
SKILL.md
Le fichier du skill reste dans le dépôt de l'éditeur.
Collez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add michael-denyer/pstack-claude --skill blast-radius -a cursor -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add michael-denyer/pstack-claude --skill blast-radius -a claude-code -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add michael-denyer/pstack-claude --skill blast-radius -a codex -yCollez la commande copiée dans un terminal. Elle installe ce SKILL.md dans cet agent.
npx skills add michael-denyer/pstack-claude --skill blast-radius -a grok -yEnvoyez le message copié dans un chat Grok Bot. Le Bot récupère ce SKILL.md sur GitHub et l'ajoute aux skills que partagent tous vos Bots.
Install this skill: https://github.com/michael-denyer/pstack-claude/tree/HEAD/plugins/pstack/skills/blast-radiusDe l'éditeur
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. Run it before design, not only before shipping, when a brief asserts something about existing code ("make endpoint X public"): the assertion is a hypothesis, and the consumer census is what decides the design.
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.
A blast-radius writeup that sounds right is worthless. It reads as convincing whether or not it's true. So don't hand back the writeup. Find the one or two facts the whole thing depends on and prove them by running code.
For each fact the change's safety depends on, get it as far down this list as is cheap, and say where it stopped.
file:line, or the library's own source.Step 4 is usually one small script that imports the same library the app ships and calls the exact function you're worried about.
why step 2 to pull the PR and commits.why. Cite a real file:line, a search that finds nothing is still an answer, and never make up a caller or an API.arena. Ask more than one model the same question and merge the answers. Different models catch different real bugs.file:line, how likely and how bad, and how to check. Paste the proof for the ones that matter.Write it through unslop, cite real code, and strip anything private before it goes anywhere public.
Reply: the writeup above, with the one safety fact either proven or marked unproven.
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X',
---name: blast-radiusdescription: Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's…---# plugins/pstack/skills/blast-radius/SKILL.mdVue d'ensemble
Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.
FAQ
Téléchargez plugins/pstack/skills/blast-radius/SKILL.md auprès de l'éditeur, ou copiez le chemin et ouvrez le dépôt. PlugMCP répertorie le skill et n'héberge pas le fichier.
L'éditeur le maintient sur https://github.com/michael-denyer/pstack-claude.
Claude, Cursor, Codex et Grok Build peuvent lire un SKILL.md que vous ajoutez depuis le dépôt de l'éditeur. Grok Bot l'installe lorsque vous envoyez dans un chat le lien du dossier GitHub du skill.