gitnexus-impact-analysis

Analyzes code change blast radius using GitNexus dependency graphs and risk scoring.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/gmolike/Claude-Template --skill gitnexus-impact-analysis-gmolike
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/gmolike/Claude-Template/tree/main/.claude/skills/gitnexus-impact-analysis
Command: npx skills add https://github.com/gmolike/Claude-Template --skill gitnexus-impact-analysis-gmolike

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before editing code, developers need to know what will break. This Skill answers questions like "Is it safe to change this function?" and "What depends on this code?" by tracing upstream dependencies and execution flows through the GitNexus code graph, then assigning a concrete risk level. ## Core Features & Use Cases - Blast Radius Analysis: Uses gitnexus_impact to find direct callers (d=1, WILL BREAK), indirect dependents (d=2), and transitive effects (d=3) for any symbol. - Pre-Commit Change Detection: Maps staged git changes to affected execution flows with gitnexus_detect_changes and reports a LOW/MEDIUM/HIGH/CRITICAL risk level. - Stale Index Guard: Mandates verifying the indexed commit matches HEAD before trusting any output, since a stale graph silently returns misleading "No changes detected" results. - Use Case: Before refactoring validateUser, run the impact workflow to discover that loginHandler and apiMiddleware call it directly and that LoginFlow and TokenRefresh processes are affected, yielding a MEDIUM risk assessment. ## Quick Start Ask the assistant to check what will break if you change a specific function, for example: "What breaks if I modify validateUser?"

Frequently Asked Questions about gitnexus-impact-analysis

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

FAQPage Schema
How do I check what code will break before changing a function?

Run gitnexus_impact with the target symbol and direction upstream to list direct callers at depth 1, which will break, plus indirect dependents at depths 2 and 3. Then check affected execution processes and assign a risk level based on the count of impacted symbols.

How to analyze the impact of staged git changes before committing?

Use gitnexus_detect_changes with scope staged to map your current git diff to affected symbols and execution flows. It returns the changed symbols, impacted processes like LoginFlow, and an overall risk rating such as MEDIUM.

Why does gitnexus_detect_changes report no changes when files were modified?

The GitNexus index is stale because it does not re-index automatically after commits. Run npx gitnexus status and compare the indexed commit to git rev-parse HEAD, then run npx gitnexus analyze if they differ.

What do the risk levels in GitNexus impact analysis mean?

Risk is based on affected symbol count: under 5 symbols is LOW, 5 to 15 is MEDIUM, over 15 or many processes is HIGH, and changes touching critical paths like auth or payments are CRITICAL regardless of count.

Can I trust gitnexus status exit code for automation?

No, npx gitnexus status exits 0 in every case, including stale or missing indexes. Parse the stdout text to compare the indexed commit against HEAD instead of branching on the exit code.