Menu

Individual skill

blast-radius

0upvotes

Prove what a small-looking change can affect before or after editing. Use for compatibility, caller, state, schema, or behavior impact analysis.

skills/blast-radius/SKILL.md

Read pinned source

Source commit 79595c97d47b5400034fb985e67f1a00389a81af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
21
Repository last updated
Nov 1, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt
# 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.