gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\"
Best for Refactoring projectsWorks with GitHub
⌘source
- author
@abhigyanpatwari- language
- TypeScript
★28kstars
3.2kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Identifies code dependencies and dependents
- ·Maps changes to affected execution flows
- ·Provides pre-commit impact assessment
- ·Uses depth-based risk classification
Use Cases
- →Assessing safety before modifying a critical function
- →Understanding what depends on a specific code component before changes
- →Checking blast radius of planned code changes before committing
Best for
- ✓Refactoring projects
- ✓Large codebases with complex dependencies
Not ideal for
- !Simple scripts without dependencies
- !Projects without GitNexus integration
FAQs
name
gitnexus-impact-analysis
description
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
Impact Analysis with GitNexus
When to Use
- "Is it safe to change this function?"
- "What will break if I modify X?"
- "Show me the blast radius"
- "Who uses this code?"
- Before making non-trivial code changes
- Before committing — to understand what your changes affect
Workflow
1. gitnexus_impact({target: "X", direction: "upstream"}) → What depends on this
2. READ gitnexus://repo/{name}/processes → Check affected execution flows
3. gitnexus_detect_changes() → Map current git changes to affected flows
4. Assess risk and report to user
If "Index is stale" → run
npx gitnexus analyzein terminal.
Checklist
- [ ] gitnexus_impact({target, direction: "upstream"}) to find dependents
- [ ] Review d=1 items first (these WILL BREAK)
- [ ] Check high-confidence (>0.8) dependencies
- [ ] READ processes to check affected execution flows
- [ ] gitnexus_detect_changes() for pre-commit check
- [ ] Assess risk level and report to user
Understanding Output
| Depth | Risk Level | Meaning |
|---|
$install
1-click copynpx skills add abhigyanpatwari/GitNexus --skill gitnexus-impact-analysisSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.