gitnexus-impact-analysis

Analyzes code change blast radius using GitNexus dependency graphs and execution flows.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill gitnexus-impact-analysis-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/gitnexus/gitnexus-impact-analysis
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill gitnexus-impact-analysis-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before editing or committing 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 mapping symbol dependencies and affected execution flows. ## Core Features & Use Cases - Blast Radius Analysis: Runs gitnexus_impact with upstream direction to find direct callers (d=1, will break), indirect dependents (d=2), and transitive effects (d=3). - Pre-Commit Change Detection: Uses gitnexus_detect_changes on staged changes to map git diffs to affected execution flows and assign a risk level. - Risk Assessment Framework: Classifies changes as LOW, MEDIUM, HIGH, or CRITICAL based on affected symbol counts, processes, and whether critical paths like auth or payments are touched. - Use Case: Before renaming a shared validation function, run the impact workflow to discover that loginHandler and apiMiddleware call it directly, then verify the LoginFlow process before committing. ## Quick Start Ask the AI to analyze 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 breaks if I change a function?

Run gitnexus_impact with the target symbol and direction set to upstream. Depth d=1 results are direct callers that will break, d=2 are likely affected, and d=3 may need testing.

How to analyze impact of staged git changes before committing?

Use gitnexus_detect_changes with scope set to staged. It maps your git diff to affected symbols and execution flows, then reports a risk level such as MEDIUM based on the number of changed symbols and affected processes.

What does the GitNexus impact depth d=1 d=2 d=3 mean?

Depth indicates dependency distance from the changed symbol. d=1 items directly call or import the target and will break, d=2 items are indirect dependents likely affected, and d=3 items are transitive effects that may need testing.

Why does GitNexus say the index is stale?

The index is stale when the dependency graph no longer matches the current codebase. Run npx gitnexus analyze in the terminal to rebuild the index before running impact analysis again.

When is a code change considered high risk?

A change is HIGH risk when it affects more than 15 symbols or many execution processes, and CRITICAL when it touches a critical path such as authentication or payments. Fewer than 5 symbols with few processes is LOW risk.