blast-radius

Trace data flow from source to all consumers and classify impact.

Updated Feb 23, 2026

Search Tags:#traceability #blast-radius #data-flow #risk-analysis #consumers #change-surface

Ready to run

npx skills add https://github.com/0xHoneyJar/construct-hardening --skill blast-radius-0xhoneyjar

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blast-radius
Source: https://github.com/0xHoneyJar/construct-hardening/tree/main/skills/blast-radius
Command: npx skills add https://github.com/0xHoneyJar/construct-hardening --skill blast-radius-0xhoneyjar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Map the complete blast radius of a data change by tracing its data flow from source to all consumers, revealing where it ends up and what surfaces it touches.

Core Features & Use Cases

Traces data flow from a source through every consumer to terminal endpoints (UI, APIs, contracts).
Produces a structured blast radius report including affected files, impact classification, and terminal consumers.
Supports embedding results in PMRs and guiding downstream hardening or testing.

Quick Start

Run a blast-radius analysis on a commit or file to generate a comprehensive data-flow map of all downstream consumers.

Frequently Asked Questions about blast-radius

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I map the blast radius of a data change across my codebase?▼

Mapping the blast radius of a data change requires tracing its data flow from the source to all consumers. This analysis identifies direct, transitive, and terminal consumers across code, APIs, and UI to classify the complete change surface.

What does data-flow traceability mean for API and UI impact analysis?▼

Data-flow traceability means tracking data from its source through every consumer to terminal endpoints like APIs and UI. It reveals exactly which surfaces and contracts are touched by a data change, ensuring comprehensive risk-analysis.

How do I trace transitive consumers when modifying a data source?▼

Tracing transitive consumers involves end-to-end data-flow mapping from the modified source. A blast-radius analysis detects all direct and downstream dependencies, generating a structured report of affected files and terminal endpoints.

Can I embed blast radius reports into PMRs for downstream hardening?▼

Yes, blast radius reports can be embedded directly into PMRs when requested. This provides a structured data-flow map of all downstream consumers, guiding downstream hardening and testing efforts across the affected change surface.

How do I identify terminal consumers affected by an API change?▼

Identifying terminal consumers affected by an API change requires tracing the data flow to its endpoints. The analysis classifies the impact and lists all terminal consumers within a structured blast radius report.

Does data-flow risk-analysis work for changes spanning code, APIs, and UI?▼

Data-flow risk-analysis applies across changes spanning code, APIs, and UI. It performs end-to-end tracing to identify direct, transitive, and terminal consumers, producing a comprehensive blast radius report for any modified data source.