gitnexus-impact-analysis

Map direct and transitive dependents to produce a prioritized impact report.

Updated Apr 10, 2026

Search Tags:#git #blast-radius #code-change #impact-analysis #dependents #risk-score

Ready to run

npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill gitnexus-impact-analysis-majedsiefalnasr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/majedsiefalnasr/bunyan-app-cursor/tree/main/.agents/skills/gitnexus-impact-analysis
Command: npx skills add https://github.com/majedsiefalnasr/bunyan-app-cursor --skill gitnexus-impact-analysis-majedsiefalnasr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly assess the impact of a proposed code change by mapping dependencies and potential ripple effects.

Core Features & Use Cases

Identify target: specify the symbol or file being changed.
Query dependents: find direct and transitive dependents across the codebase.
Assess blast radius: categorize impact into direct and transitive effects.
Risk scoring: assign Low/Medium/High/Critical risk and suggest mitigations.
Use Case: When about to modify a core library function, generate an impact report showing affected modules and suggested safe alternatives.

Quick Start

Provide the target symbol or file and run the analysis to generate the impact report.

Frequently Asked Questions about gitnexus-impact-analysis

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

FAQPage Schema

How do I analyze the blast radius of a code change before committing?▼

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.

What is impact analysis for code changes and when do I need it?▼

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.

How do I check direct and transitive dependents when modifying a shared library?▼

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.

How are risk scores calculated for repository code modifications?▼

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.

Can I generate a prioritized impact report for a specific file change?▼

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.

What are the limitations of automated blast radius analysis?▼

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.