blast-radiuslisted
Install: claude install-skill ychampion/ystack
# Blast radius
A diff shows what changed. It doesn't show who depended on the old behaviour. This skill finds those
dependents, sorts them by risk, and settles the riskiest one with a real run.
## When it applies
- A change touches something other code reads: a function signature or return value, a type, a
default, an error it throws, a config or env key, a file or wire format, a route, a CLI flag, a
database column, an event name.
- Something is deleted, renamed or moved.
- Someone asks "is this safe?" and the honest answer is "probably".
Skip it for changes nothing else can observe: a private helper's internals with unchanged behaviour,
comments, tests only.
## Procedure
### 1. Name the behaviour change, not the code change
Write one line per observable difference, old → new. "Renamed `parse` to `parseConfig`" is a code
change; "`parse` no longer exists; `parseConfig` throws on an empty file where `parse` returned `{}`"
is two behaviour changes. Everything after this step works from these lines.
### 2. Find every consumer, including the ones grep misses
Static references first: callers, importers, subclasses, type users. Then the dynamic ones, which are
where breakage hides:
- names held as strings: config keys, route paths, event names, feature flags, reflection, `getattr`,
dependency-injection tokens, SQL column names;
- data already on disk or in flight: saved files, caches, queues, database rows, cookies, other
services' payloads, written in the old fo