gitnexus-impact-analysis

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

3|5|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill gitnexus-impact-analysis-bensheridanedwards
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/BenSheridanEdwards/ArchitectPlaybook/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis
Command: npx skills add https://github.com/BenSheridanEdwards/ArchitectPlaybook --skill gitnexus-impact-analysis-bensheridanedwards

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?" by tracing upstream dependencies and mapping changes to affected execution flows. ## Core Features & Use Cases - Blast Radius Analysis: Uses the GitNexus impact tool to find direct callers (d=1, will break), indirect dependents (d=2), and transitive effects (d=3) for any symbol. - Pre-Commit Change Detection: Runs detect_changes on staged git changes to map modifications to affected execution processes and assign a risk level. - Risk Assessment: Classifies changes as LOW, MEDIUM, HIGH, or CRITICAL based on affected symbol counts, process involvement, and whether critical paths like auth or payments are touched. - Use Case: Before renaming a shared validateUser function, run the impact workflow to discover that loginHandler and apiMiddleware call it directly and that the LoginFlow process depends on it, then decide whether the change is safe. ## Quick Start Ask the assistant to analyze what will break if you change a specific function, for example: "What is the blast radius 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 will break before changing a function?

Run the impact tool with the target symbol and direction set to upstream. Direct callers at depth 1 will break, depth 2 items are likely affected, and depth 3 items may need testing. Review high-confidence dependencies above 0.8 first.

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

Use detect_changes with the scope set to staged. It maps your modified symbols to affected execution processes and returns a risk rating such as MEDIUM, so you can judge whether the commit is safe.

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

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

Why does the impact analysis say the index is stale?

A stale index means the GitNexus dependency graph no longer matches the current code. Run node .gitnexus/run.cjs analyze in the terminal to rebuild the index, then retry the impact query.

When is a code change considered high or critical risk?

Changes affecting more than 15 symbols or many execution processes are HIGH risk. Any change touching a critical path such as authentication or payments is classified as CRITICAL regardless of symbol count.