blast-radius-check

To check the blast radius of a code change, search all repositories for the target symbol, enumerate every referencing file and service, and produce an impact analysis listing caller counts, transitive dependencies, and recommended mitigations.

Cross-repo impact analysis discovers every caller and dependent of a code symbol across repositories before modification. You need it during refactoring, hotfixes, or API contract changes to prevent breaking transitive consumers and unrelated services.

Trace transitive callers before modifying a shared utility by performing systematic cross-repo text and import searches, tracing data and control flow, and filling a touchpoint checklist to verify all direct callers, subclasses, tests, and config dependencies.

Yes, impact analysis works for API contract changes and field renames by categorizing dependents into direct callers, subclasses, tests, and config, then applying decision rules based on caller counts to recommend specific mitigation actions.

The best way to map consumers before applying a hotfix is to systematically search for symbol usages, imports, and interface implementations across repositories, classify the dependents, and output an impact analysis with recommended mitigation actions.