blast-radius-check

What problem does it solve?

Prevents unintended breakages by discovering every caller and dependent before changing existing code so fixes do not break unrelated services or components. It addresses the common failure mode of assuming a change is isolated when transitive consumers exist.

Core Features & Use Cases

• Cross-repo impact discovery: Systematic guidance to search for symbol usages, imports, and interface implementations across repositories.
• Categorization and decision rules: Helps classify dependents (direct callers, subclasses, tests, config) and recommends actions based on caller counts.
• Data-flow tracing and verification: Promotes tracing data/control flow for multi-component changes and mandates filling a touchpoint checklist before edits.
• Use cases include refactoring shared utilities, applying hotfixes, renaming fields or API contracts, and any change that might propagate across services.

Quick Start

Search all repositories for the symbol you plan to modify, enumerate every referencing file and service, and produce an impact analysis that lists caller counts, transitive dependencies, and recommended mitigations.