gitnexus-impact-analysis

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

1|Updated Jul 27, 2023
One-click install
npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-impact-analysis-alextheguitarguy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/AlexTheGuitarGuy/.dotfiles/tree/main/claude/.claude/skills/gitnexus-impact-analysis
Command: npx skills add https://github.com/AlexTheGuitarGuy/.dotfiles --skill gitnexus-impact-analysis-alextheguitarguy

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 index, then assigning a risk level to the change. ## Core Features & Use Cases - Symbol Blast Radius: Runs impact analysis with upstream direction to list direct callers (d=1 WILL BREAK), indirect dependents (d=2), and transitive effects (d=3) with confidence scores. - Pre-Commit Change Detection: Uses git-diff based detect_changes to map uncommitted edits to affected execution processes and an overall risk rating. - Risk Gating: Classifies changes as LOW, MEDIUM, HIGH, CRITICAL, or UNKNOWN, treating zero-caller results as unresolved rather than safe until confirmed by text search. - Use Case: Before renaming a shared validateUser function, run the workflow to discover that loginHandler and apiMiddleware call it directly and that LoginFlow and TokenRefresh processes depend on it, yielding a MEDIUM risk report. ## Quick Start Ask the assistant to check what will break if you change a specific function before you edit it.

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 will break before changing a function?▼

Run impact analysis with the target symbol and upstream direction to list its callers by depth. Direct callers at d=1 will break, d=2 are likely affected, and d=3 may need testing, giving you a risk level before editing.

How to run a pre-commit impact check on uncommitted changes?▼

Use detect_changes with scope set to all, which diffs the working tree and maps changed symbols to affected execution processes. It returns a risk rating such as LOW, MEDIUM, or HIGH for the pending commit.

What if the GitNexus MCP tools are unavailable?▼

Use the CLI fallback by running node .gitnexus/run.cjs with the impact or detect-changes subcommands and the --repo flag. If run.cjs is missing, replace it with npx gitnexus in the same commands.

Why does impact analysis show zero callers for a used function?▼

Zero callers means UNKNOWN risk, not safe. Dynamic dispatch, plain-object property access, or cross-language calls can hide callers from the index, so confirm with a text search before treating the symbol as unused.

Does impact analysis work with multiple indexed repositories?▼

Yes, but you must pass the repo argument on every call once more than one repository is indexed. Call list_repos first to bind the correct repository, and ask the user if the intended target is ambiguous.

Why does detect_changes report zero changed symbols incorrectly?▼

A wrong-worktree zero happens when the server diffs a different checkout than the one you edited, and it carries no warning flags. Pass the worktree parameter for linked worktrees and confirm the diffed checkout matches your edits.