Blast Radius
Blast radius: what a change breaks beyond its diff, with the one safety fact proven by running real code. Use for 'blast radius of X' or 'what could this break', a small diff you don't trust, choosing E2E scenarios when the reach is unclear, or a review whose diff touches shared interfaces, schemas, wire formats, or flags.
Install
npx skills add Dimon94/skills --skill blast-radiusgit clone --depth 1 https://github.com/Dimon94/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/blast-radius ~/.claude/skills/blast-radiusPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Blast radius Find what a change breaks somewhere else, before it ships. Use for "blast radius of X", "what could this break", or reviewing a small diff you don't trust yet. Companion to `how` and `why`. `how` tells you what the code does. `why` tells you why it's shaped that way. Blast radius tells you what it breaks somewhere else. Listing the callers is not the job. The agent can grep those in a second. The job is the breakage grep won't show you. ## Don't trust your own writeup A blast-radius writeup that sounds right is worthless. It reads as convincing whether or not it's true. So don't hand back the writeup. Find the one or two facts the whole thing depends on and prove them by running code. ### How sure are you For each fact the change's safety depends on, get it as far down this list as is cheap, and say where it stopped. 1. You said so. Worthless on its own. 2. You pointed at the line. A real `file:line`, or the library's own source. 3. You showed the bad case can't happen. You walked the failure step by step and it doesn't reach. 4. You ran it. A script or test that calls the real code and fails loud if you're wrong. 5. You reproduced it in the running app. Step 4 is usually one small script that imports the same library the app ships and calls the exact function you're worried about. ## Steps
Details
- Skill name
blast-radius- Repository
- Dimon94/skills
- Path
skills/blast-radius/SKILL.md- Repo updated
- 18 November 2026
FAQ
What does the Blast Radius skill do?
Blast radius: what a change breaks beyond its diff, with the one safety fact proven by running real code. Use for 'blast radius of X' or 'what could this break', a small diff you don't trust, choosing E2E scenarios when the reach is unclear, or a review whose diff touches shared interfaces, schemas, wire formats, or flags.
How do I install the Blast Radius skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dimon94/skills --skill blast-radius. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Blast Radius popular?
It lives in Dimon94/skills, which has 107 GitHub stars and 21 forks.
Related skills
Maintain Verification Skill
107Dimon94/skills
Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or "audit the verify skill".
Create Verification Skill
107Dimon94/skills
Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.
How
107Dimon94/skills
Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer"). Explains subsystem architecture, runtime flow, onboarding mental models. Use why for motivation.
Customizing Vectors R
67jeremy-allen/claude-skills
Type-stable vector operations and custom vector classes using vctrs. Use this skill when building R packages with custom types, need guaranteed output types regardless of input values, implementing consistent coercion/casting rules, or creating vector classes that work seamlessly with data frames. Covers when to use vctrs vs base R, building custom vector classes, coercion methods, and testing vctrs classes.
Skill Testing
115javiarmesto/ALDC-AL-Development-Collection
AL test development patterns for Business Central. Use when creating test codeunits, writing Given/When/Then test procedures, using Library Assert, configuring test projects, or implementing TDD workflows.
Diagnose
43aws-samples/sample-kiro-cli-multiagent-development
Investigate and fix open issues in the .kiro/issues/ folder using test-first debugging. Use when asked to diagnose, triage, or work through unresolved bug reports, or when the user mentions open issues that need fixing.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.