gitnexus-impact-analysis

To analyze the blast radius of a code change, you provide the target symbol or file to map its direct and transitive dependents. This generates an impact report that categorizes ripple effects and assigns a risk score to safeguard your modifications.

Impact analysis for code changes identifies the potential ripple effects of modifying a specific symbol or file across your repository. You need it when altering core library functions to prevent breaking direct and transitive dependents.

Checking direct and transitive dependents involves querying the repository for all modules relying on your target symbol or file. The analysis maps these relationships to reveal the full blast radius and highlight affected areas.

Risk scores for code modifications are calculated deterministically by evaluating the mapped blast radius of direct and transitive dependents. The analysis assigns explicit Low, Medium, High, or Critical risk categories and suggests appropriate mitigations.

Yes, you can generate a prioritized impact report by specifying the target file being changed. The analysis queries dependents across the codebase and produces a concise summary with explicit risk categories for review.

Automated blast radius analysis relies on mapping explicit symbol and file dependencies, meaning it may not capture dynamic runtime dependencies. It provides deterministic scoring based on static code relationships to suggest mitigations rather than guarantee zero regressions.