Menu

Individual skill

blast-radius

Before a change merges, find what it can break beyond the lines it touches, and prove by running code the one fact its safety depends on. Use for "what's the blast radius", "what could this break", "review this small diff I'm nervous about".

plugins/requie/endostack/skills/blast-radius/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 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)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

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

Find what a change can break beyond the lines it touches, and prove by execution the single fact its safety depends on.

The [how](../how/SKILL.md) skill answers how code works and the [why](../why/SKILL.md) skill answers why it is that way. This skill answers what else the change damages. Listing call sites is not the goal; a symbol search does that in a second. The goal is the failure modes a symbol search cannot see.

A convincing written analysis proves nothing by itself, because a wrong analysis reads just as well as a right one. So isolate the one or two facts the change's safety rests on and demonstrate them by running code.

## Evidence ladder

For every fact the safety depends on, climb as high as is cheap and report the level reached.

1. **Claimed.** Someone said so. Worth nothing alone.
2. **Located.** A specific file and line, in this repo or in the dependency's own source.