- name
SKILL.md
El archivo de la skill permanece en el repositorio del publicador.
Pega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add backnotprop/pstack --skill blast-radius -a cursor -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add backnotprop/pstack --skill blast-radius -a claude-code -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add backnotprop/pstack --skill blast-radius -a codex -yPega el comando copiado en una terminal. Instala este SKILL.md en ese agente.
npx skills add backnotprop/pstack --skill blast-radius -a grok -yEnvía el mensaje copiado en un chat de Grok Bot. El Bot obtiene este SKILL.md de GitHub y lo añade a las skills que comparten todos tus Bots.
Install this skill: https://github.com/backnotprop/pstack/tree/HEAD/skills/blast-radiusDel publicador
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.
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.
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…---# skills/blast-radius/SKILL.mdResumen general
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', or reviewing a small diff you don't trust.
Preguntas frecuentes
Descarga skills/blast-radius/SKILL.md desde el publicador, o copia la ruta y abre el repositorio. PlugMCP lista la skill y no aloja el archivo.
El publicador lo mantiene en https://github.com/backnotprop/pstack.
Claude, Cursor, Codex y Grok Build pueden leer un SKILL.md que añadas desde el repositorio del publicador. Grok Bot lo instala cuando envías en un chat el enlace a la carpeta de la skill en GitHub.