gitnexus-impact-analysis

Code blast radius analysis identifies which downstream symbols and execution flows will break before you modify a target symbol. You need it for refactors, bugfixes, and pre-commit validation to ensure dependency depth and confidence levels are assessed safely.

To check the impact of refactoring a core function, analyze upstream dependencies to map direct callers and transitive effects. This pre-commit validation reports depth-based risk categories from LOW to CRITICAL, highlighting affected execution flows to review.

Yes, you can detect the blast radius of staged git diffs by running diff-scoped detection. This maps your current changes to likely affected flows and symbols, helping you validate code safety and prioritize tests before committing.

Dependency depth affects risk assessment by classifying transitive effects into categories like LOW, MEDIUM, HIGH, or CRITICAL. Direct callers represent a lower risk, while deeper transitive dependencies across execution flows indicate a higher blast radius and require checking first.

Yes, impact analysis works for both bugfixes and major refactoring tasks by evaluating the blast radius of any modified code symbol. It applies to both targeted changes and broader refactors, reporting confidence levels and affected flows regardless of scope.