blast-radius

Analyzes what a code change could break beyond the diff and proves safety facts by running real code.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/mmdmcy/fluttAIrbar --skill blast-radius-mmdmcy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: blast-radius
Source: https://github.com/mmdmcy/fluttAIrbar/tree/main/plugins/pstack/skills/blast-radius
Command: npx skills add https://github.com/mmdmcy/fluttAIrbar --skill blast-radius-mmdmcy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss breakage that grep and symbol search cannot find, such as changes to API responses, wire formats, feature flags, or downstream consumers. This Skill identifies the real risks of a change before it ships and proves the key safety assumption by executing actual code instead of trusting a convincing writeup. ## Core Features & Use Cases - Hidden Breakage Detection: Traces risks that symbol search misses, including JSON payloads, DB columns, wire formats, cross-language consumers, and code several hops downstream. - Proof Over Prose: Ranks each safety fact on a five-level confidence ladder and requires running a script or test against the real code before calling anything proven. - Honest Risk Reporting: Separates confirmed risks with file:line citations from checked-and-cleared cases, and marks anything unproven instead of rounding up. - Use Case: Before merging a diff that touches a shared cache invalidation function, use this Skill to find the one fact the change is safe because of, write a small script that calls the real function, and ship the proof alongside the risk list. ## Quick Start Ask the assistant to analyze the blast radius of your current diff and prove the one fact it is safe because of by running real code.

Frequently Asked Questions about blast-radius

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

FAQPage Schema
How do I find the blast radius of a code change?▼

Read the diff and the symbols it changes, then find the one fact the change is safe because of. Trace what grep misses, such as API responses, DB columns, and feature flags, and prove the key fact by running a script against the real code.

How to review a diff for breakage that grep cannot find?▼

Grep only finds direct callers. Check the library source and pinned versions, timing behavior like microtasks and teardown, serialized data formats, other languages reading the same bytes, and code several hops downstream of the change.

Why is a written risk analysis not enough before merging?▼

A convincing writeup reads as true whether or not it is, so the Skill requires proving safety facts by running real code. Facts are ranked on a five-level confidence ladder, and anything not proven by execution is explicitly marked unproven.

Can blast radius analysis handle large or wide changes?▼

Yes. For big or wide changes the Skill recommends running the analysis as an arena, asking several models the same question and merging the answers, since different models catch different real bugs.

What are the limitations of automated blast radius checks?▼

The analysis depends on the reviewer's ability to identify the right safety fact and write a cheap proof script. If a fact cannot be proven cheaply, it is reported as unproven rather than settled, so residual risk may remain.