Skip to content
Back to skills

Blast Radius Preview

ASecurity

Show the likely downstream consequences of a proposed change — hidden dependencies, fragile integration points, and predicted breakage categories.

  • 3 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 9, 2026
ai-agentsgonodeapiperformance

Works with

  • api

Security analysis

A100/100

Scanned October 9, 2026

npx -y skills add alisattorov06/ali-kiro --skill blast-radius-preview --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Blast Radius Preview?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Blast Radius Preview
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/alisattorov06-blast-radius-preview/badge)](https://www.skillsdirectory.com/skills/alisattorov06-blast-radius-preview)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: blast-radius-preview
description: Show the likely downstream consequences of a proposed change — hidden dependencies, fragile integration points, and predicted breakage categories.
origin: FlowDeck
---

# Blast Radius Preview

Before committing to a change, map every system that could break. Activate this skill by providing a change description to the agent.

## When to Activate

- Before merging a change that touches shared infrastructure
- Before modifying a public API, event schema, or DB model
- Before changing authentication or session handling
- Any time the Impact Radar returns HIGH

## Workflow

1. Load the dependency graph from `~/.fd-plan/<slug>/.codebase/MEMORY.json`
2. Start from the directly changed nodes
3. Walk the graph outward: find all services/modules that depend on the changed node
4. At each hop, check:
   - Is this an integration point (API call, event subscription, DB query)?
   - Does this path have regression history in `~/.fd-plan/<slug>/.codebase/FAILURES.json`?
   - Is this path covered by integration tests?
5. Flag hidden couplings: shared mutable state, ambient context, feature flags
6. Produce the blast radius map

## Blast Radius Report Format

```markdown
## Blast Radius Report

### Change
[description]

### Direct Blast (depth 1)
| Module | Coupling Type | Test Coverage | Fragile? |
|--------|--------------|---------------|---------|

### Indirect Blast (depth 2–3)
| Module | Via | Risk Level |
|--------|-----|------------|

### Integration Point Risks
- [endpoint/event]: [why at risk]

### Hidden Couplings
- [module]: shared state / ambient context / feature flag

### Predicted Breakage Categories
- [ ] Performance: [reason]
- [ ] Auth: [reason]
- [ ] Schema: [reason]
- [ ] Async flow: [reason]

### Blast Radius: NARROW | MODERATE | WIDE
```

## Guidance

- NARROW: ≤3 downstream modules, all covered by tests → safe to proceed
- MODERATE: 4–10 downstream modules or ≥1 uncovered → add tests before merging
- WIDE: >10 downstream modules or hits fragile integration → escalate to senior review

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.