Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Blast Radius
1. Name the changed contract: type, value, state transition, API, storage shape, timing, style token, or side effect.
2. Enumerate direct readers/writers/callers and any serialized/public boundaries.
3. Trace transitive assumptions by search, type references, tests, runtime wiring, and history as available.
4. Identify the strongest fact that would make the change safe and prove that fact by running or inspecting code when possible.
5. Return affected surfaces grouped as definite, plausible, and ruled out with evidence. Never write "safe" without the proof behind it.
The line at the top of this page pins the label git:20260908.ec65ed5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_m73qcybkpf54xk2j
GET https://markdownregistry.com/api/v1/resolve?ref=theonlyfusioncube/potetos-for-everyone/blast-radius
GET https://markdownregistry.com/api/v1/blob/fd544d34a7dd76708b106e3f5c0177aff1c656b455c03742f53cd8435d9c1fd0
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
theonlyfusioncube/potetos-for-everyone · automations/benny/skills/reproduce-and-fix-issues/SKILL.md · Reproduce a confirmed issue on the closest real surface, find root cause, and optionally prepare a minimal draft fix…
theonlyfusioncube/potetos-for-everyone · automations/benny/skills/triage-issue-reports/SKILL.md · Triage incoming software issue reports using available repository and runtime evidence, without editing code. Use for…
theonlyfusioncube/potetos-for-everyone · skills/architect/SKILL.md · Settle data shapes, ownership, boundaries, and interfaces before code crosses a function/module boundary. Use for…
theonlyfusioncube/potetos-for-everyone · skills/arena/SKILL.md · Spawn parallel candidate implementations for the same task, cross-judge, and graft the best parts into the winning…
theonlyfusioncube/potetos-for-everyone · skills/automate-me/SKILL.md · Create a personal mode skill from recurring workflow patterns in available history. Use when the user wants their own…
theonlyfusioncube/potetos-for-everyone · skills/benchmark-checklist/SKILL.md · Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened)…
theonlyfusioncube/potetos-for-everyone · skills/bro/SKILL.md · Restate the last technical explanation in plain human language with minimal jargon. Use when the user asks for a…
theonlyfusioncube/potetos-for-everyone · skills/correct/SKILL.md · Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types…
theonlyfusioncube/potetos-for-everyone · skills/create-formal-verification-skill/SKILL.md · Generate a project-local skill that formally verifies the code where a bug costs the most and tests reach the least, in…
theonlyfusioncube/potetos-for-everyone · skills/create-verification-skill/SKILL.md · Generate a project-local verification skill that drives the real app and captures evidence. Use when setting up…
theonlyfusioncube/potetos-for-everyone · skills/figure-it-out/SKILL.md · Design a rigorous custom playbook when no bundled playbook safely fits a large or unusual task. Use for cross-cutting…
cursor/plugins · pstack/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
cursor/plugins · harness/pstack/claude-code/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
michael-denyer/pstack-claude · plugins/pstack/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
backnotprop/pstack · skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
pedrohcgs/claude-code-my-workflow · .claude/skills/blast-radius/SKILL.md · Before and after changing anything shared — a function's return value, a signature, a schema, a label set, a config…
pixeltable/pixeltable · .claude/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
athola/claude-night-market · plugins/pensive/skills/blast-radius/SKILL.md · Analyzes code change impact with risk scoring and affected-node mapping. Use before merging to understand what a change…
parcha-ai/parcha-skills · blast-radius/skills/blast-radius/SKILL.md · Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe…
