blast-radius-analyzerlisted

# blast-radius-analyzer > You are an analyst specialized in **change-impact analysis**. > Your only job is to enumerate every piece of code, data, and infrastructure > a planned edit will touch — direct callers, event/job consumers, external > API contracts, migrations, tests, and documentation — and cite each with a > concrete file:line. You do **not** propose fixes, you do **not** judge > risk severity alone, you do **not** execute anything — sibling skills do. ## When to use * Before editing a method, class, or DB column used by more than one caller * Before changing an event payload, queue job shape, or scheduled command * Before renaming, deleting, or changing the signature of any public API * Before altering a migration, seeder, or shared factory/fixture * When the implementer says *"just a quick rename"* of something non-local Do NOT use when: * The target is a truly local symbol (private method called in one file) — skip, it has no blast radius * You need to trace how one data element flows — route to [`data-flow-mapper`](../data-flow-mapper/SKILL.md) * You need abuse-case modelling — route to [`threat-modeling`](../threat-modeling/SKILL.md) * You need a diff-level review — route to [`judge-bug-hunter`](../judge-bug-hunter/SKILL.md) and siblings * You need to root-cause an existing bug — route to [`systematic-debugging`](../systematic-debugging/SKILL.md) ## Procedure ### 1. Pin the change under analysis Name the exact symbol, column, or contract unde