blast-radius

Map potential breakage across code, tests, docs, and deployments into a date-stamped markdown report.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill blast-radius-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blast-radius
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/blast-radius
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill blast-radius-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This piece identifies and communicates potential failure points before any destructive or risky change, providing a structured, confidence-tagged forecast to guide decision-making and mitigation.

Core Features & Use Cases

  • Read-only by default: the skill generates a comprehensive blast-radius report without performing edits or migrations.
  • Change-capture workflow: users describe the intended change to tailor the scan and surface relevant dependencies, tests, docs, and deployments.
  • Output-centric: writes the report to docs/blast-radius/<YYYY-MM-DD>-<slug>.md for verifiable post-change review.
  • Scoping and safety: tags findings with Verified, Likely, and Possible to help prioritize remediation and validation.

Quick Start

Describe the planned change and run this skill to generate the blast-radius report.

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 risky codebase change before executing it?

To map blast radius before destructive changes like schema migrations or refactors, describe your intended change and run a read-only scan across code, tests, docs, and deployments to generate a structured impact-analysis report.

What is a pre-mortem impact analysis for a major dependency bump or service rename?

A pre-mortem impact analysis identifies potential failure points across your codebase before a risky change, producing a confidence-tagged forecast of verified, likely, and possible findings to guide mitigation.

How do I perform a read-only risk analysis for a schema migration without modifying my codebase?

You perform a read-only risk analysis by describing the planned migration to tailor a scan that surfaces relevant dependencies, tests, and docs, generating a blast-radius report without performing edits or migrations.

Can I generate a blast-radius report for large refactors and file path moves?

Yes, you can generate a blast-radius report for large refactors and file path moves by scanning code, tests, docs, and deployments, tagging findings as verified, likely, or possible to help prioritize remediation.

Where does the impact-analysis report get saved after scanning a codebase for risky changes?

The impact-analysis report is saved as a date-stamped markdown file at docs/blast-radius/<YYYY-MM-DD>-<slug>.md, providing a verifiable record for post-change review with no automatic modifications applied.

What are the limitations of automated change-management risk analysis?

The change-management risk analysis is read-only and makes no automatic modifications, meaning it cannot execute migrations or apply fixes, and its findings are tagged with confidence levels requiring manual validation.