lootlog/monorepo / .agents/skills/blast-radius
blast-radius
VerifiedAssess what a code change can break beyond its direct diff and prove the key safety assumptions with executable evidence. Use for risky reviews, cross-workspace changes, generated contracts, migrations, shared packages, queues, WebSockets, or requests such as "what could this break?".
Blast radius
Find the indirect failure modes before a change ships.
Workflow
- Read the diff, affected symbols, package boundaries, schemas, generated artifacts, and relevant tests.
- If
.codegraph/exists, use CodeGraph before text search to trace callers, callees, and package relationships. - State the one or two facts that make the change safe. Do not hide assumptions inside a long risk list.
- Trace where symbol search stops: OpenAPI contracts, database columns, serialized events, Redis keys, queue payloads, generated clients, environment variables, and consumers in other workspaces.
- Classify each meaningful risk by likelihood, impact, and the cheapest check that would expose it.
- Prove the key safety fact with the narrowest real check available: a focused test, a script against production code, an existing running application, or direct inspection of a generated artifact. Do not start an application in this repository.
- Run adjacent validation in proportion to the risk.
Report
Return:
- what behavior changed;
- the key safety fact and the strongest evidence reached;
- confirmed risks with concrete paths and checks;
- risks investigated and cleared;
- the smallest pre-merge verification still needed.
Mark an assumption as unproven when it cannot be checked cheaply. A plausible explanation is not proof.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |