blast-radius ยท diff
git:20260906.cc9d07d to git:20260909.82ed8e3
1 added, 0 removed. Audit A to A.
What this update changes in the checks
No check changed: every fixed check gives the same answer before and after this update.
A tripped check is a label, not a verdict: read the matched text and the lines below. This week's updates that newly trip a check.
---
+ disable-model-invocation: true
name: blast-radius
description: "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."
---
# 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.
Use [code-review](../code-review/SKILL.md) to establish the requested diff and review boundary. Focus this workflow on effects beyond that diff. Inspect source and history directly; no companion explanation skill is required.
Keep an impact assessment read-only. Run probes against isolated fixtures or the repository's existing test environment, preserving unrelated work. A request to prove a safety assumption does not authorize live-system writes, external-model context transfers, or publication.
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.
1. You said so. Worthless on its own.
2. You pointed at the line. A real `file:line`, or the library's own source.
3. You showed the bad case can't happen. You walked the failure step by step and it doesn't reach.
4. You ran it. A script or test that calls the real code and fails loud if you're wrong.
5. You reproduced it in the running app.
Any safety fact you can't get to step 4, say so out loud. Don't write it up as settled. Step 4 is usually one small script that imports the same library the app ships and calls the exact function you're worried about.
## Steps
1. Read the change, including added, changed, and deleted symbols and behavior not obvious from the diff. Inspect relevant `git log`, `git show`, and `git blame` history and available PR context. Record the reviewed revisions and separate documented intent from inference. Missing PR access does not prevent local source inspection, but remains an evidence limit.
2. Find the one fact it's safe because of. Most changes that look scary are safe because of a single fact, like "this call only drops already-dead cache entries and does nothing else". Find that fact. If it holds, most of the scary cases die at once. Spend your time here, not on a long list of maybes.
3. Look where grep stops. Read the source of the library you call, and check its pinned version and any local patch. Work out when things run: microtasks, unmount and teardown, Solid versus React. Follow what a symbol search misses: the JSON an API returns, a DB column, a wire format, another language reading the same bytes, a feature flag, code three hops downstream.
4. Separate impact, likelihood, and confidence. Keep confirmed risks apart from checked-and-cleared paths and unresolved assumptions. Cite actual source locations and inspected consumers. A search with no matches does not prove the absence of dynamic or external callers.
5. Prove the one fact. Write a script or test that runs the real code, run it, and paste what happened. If you can't prove it cheaply, mark it unproven. Don't round up.
6. For a broad change, use code-review's [independent review procedure](../code-review/references/independent-reviews.md) when delegation is available, permitted, and useful. Assign concrete boundaries and reconcile findings against evidence. Otherwise finish the assessment locally and state the review coverage; no separate orchestration or model service is required.
## What to hand back
- **What it does.** What changed, including the part that isn't obvious.
- **The one fact it's safe because of.** State it, say which step you got it to, and show the proof. If you couldn't prove it, write unproven.
- **Risks.** Only the real ones. Each names how it breaks, the `file:line`, how likely and how bad, and how to check. Paste the proof for the ones that matter.
- **Cleared.** What you checked and why it's fine.
- **Before you merge.** The cheapest test or repro that catches the real bug, including the script you wrote.
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.