blast-radius · git:20261108.ac1df7f · 2026-11-08 · sha256 7f189876c496d5ca
blast-radius git:20261108.ac1df7fA
Immutable. This exact content never changes and is served at /api/v1/blob/7f189876c496d5ca.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3kkfmgeocddezsm6/7f189876c496d5caaa622cec9d01705314883397cc3efb3622cf0cd512d669b9.json
Then /plugin install blast-radius@markdownregistry-3kkfmgeocddezsm6 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: blast-radius
description: "Map what a change could break beyond the diff — dependents found by search and AST, classified certain/likely/unlikely — and prove the certain and likely ones by running their checks. Before risky refactors or signature changes."
aliases: []
metadata:
credits:
impact-analysis: pstack
author: Lauren Tan
url: "https://github.com/cursor/plugins/tree/main/pstack"
port: pstack-claude
port-author: Michael Denyer
port-url: "https://github.com/michael-denyer/pstack-claude"
---
# Blast Radius
The diff tells you what changed; it does not tell you what breaks. This
skill maps the dependents of a change and proves what it can — by running
code, not by reasoning alone.
## When to use
- a signature, data shape, or behavior other code calls changed
- a dependency bump, config default flip, or migration
- the user asks "what could this break?"
## Workflow
1. **Name the change surface**: exported symbols, persisted formats, CLI
flags, API contracts, timing assumptions. List them explicitly.
2. **Map dependents**: grep for each symbol; where available use AST search
(`ast_grep_search` MCP tool) to catch structural uses text search misses;
follow re-exports one more hop than feels necessary.
3. **Classify each dependent**:
- **certain** — calls the changed surface directly
- **likely** — consumes a type or format the change touches
- **unlikely** — shares a module but not the surface
4. **Prove what you can**: for every certain and likely impact, run the
exact check that would catch the break — its test, its typecheck, its
build, or a one-off command exercising the path. Report real output.
Impacts you cannot execute a check for are listed as **unverified**, not
as safe.
5. **Report**: the surface, the dependent counts by class, per-impact
verification with evidence, and the unverified remainder named honestly.
## Rules
- "It should be fine" is not a classification; every claim is certain,
likely, unlikely, or unverified, with its reason in the same sentence.
- Reasoning reduces the search space; execution settles the verdict.
- The report never edits code; fixes found this way go through `execute`.