blast-radius

Identify consumers and dependencies of exported symbols before modification.

1|Updated Dec 15, 2025

Search Tags:#refactor #blast-radius #code-change #impact-analysis #dependency-tracing #shared-code

Ready to run

npx skills add https://github.com/maxtheman/mcpManager --skill blast-radius

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: blast-radius
Source: https://github.com/maxtheman/mcpManager/tree/main/mx_source/skills/blast-radius
Command: npx skills add https://github.com/maxtheman/mcpManager --skill blast-radius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Before modifying shared code (types, APIs, utilities), blast-radius assessment identifies all consumers of exported symbols to prevent partial migrations and broken integrations.

Core Features & Use Cases

Find all impacted consumers across files and modules before changes.
Map dependencies and generate a concrete update plan to minimize regressions.
Guardrails for refactors by surfacing potential breaking changes early and guiding safe transitions.

Quick Start

Run a blast-radius assessment on your repository to enumerate all exported symbols and their consumers before making changes.

Frequently Asked Questions about blast-radius

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

FAQPage Schema

How do I find all consumers of an exported symbol before modifying shared code?▼

Impact analysis for code changes identifies all consumers and dependencies of exported symbols across files and packages. It indexes references to map impact and prevent partial migrations or broken integrations in shared codebases.

How do I map dependencies and generate an update plan for a code refactor?▼

To map dependencies for a code refactor, assess the blast-radius of exported symbols to enumerate all consumers. This generates a concrete update plan that guides safe transitions and minimizes regressions during the migration.

What is the best way to prevent breaking changes when modifying shared utilities?▼

The best way to prevent breaking changes when modifying shared utilities is to proactively trace their blast-radius. This surfaces potential breaking changes early by identifying all impacted consumers across modules before shipping the code change.

Can I use impact analysis to trace dependencies across multiple packages in a shared codebase?▼

Yes, you can use impact analysis to trace dependencies across multiple packages in a shared codebase. The assessment specifically applies to environments where exported symbols span multiple files or packages to map downstream impact.

When do I need to run a dependency tracing assessment before a code change?▼

You need to run a dependency tracing assessment before modifying any exported symbols in shared code. It is required when updating types, APIs, or utilities to ensure partial migrations do not break existing integrations.