skills.rest
changfengpro
changfengproCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gitnexus-impact-analysis

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

Updated May 28, 2026
Search Tags:#impact analysis#risk assessment#pre-commit#code safety#dependency graph#blast radius#gitnexus
One-click install
npx skills add https://github.com/changfengpro/agent-skills --skill gitnexus-impact-analysis-changfengpro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/changfengpro/agent-skills/tree/main/skills/gitnexus-impact-analysis
Command: npx skills add https://github.com/changfengpro/agent-skills --skill gitnexus-impact-analysis-changfengpro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before editing code, developers often cannot tell what will break downstream. This Skill answers questions like "Is it safe to change X?" and "What depends on this function?" by mapping symbol dependencies and execution flows before you commit. ## 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 Risk Checks: Uses gitnexus_detect_changes on staged git changes to map edits to affected execution flows and assign a LOW/MEDIUM/HIGH/CRITICAL risk level. - Use Case: Before renaming a shared function like validateUser, run the impact workflow to discover that loginHandler and apiMiddleware call it directly and that the LoginFlow and TokenRefresh processes are affected, then report a MEDIUM risk to the team. ## Quick Start Ask the assistant 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 will break if I change a function?▼

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

How to analyze git changes before committing code?▼

Use gitnexus_detect_changes with scope set to staged. It maps your current git diff to affected symbols and execution flows, then reports a risk level such as LOW, MEDIUM, or HIGH.

What does the GitNexus impact depth d=1 mean?▼

Depth d=1 marks direct callers or importers of the target symbol, meaning they will break if the symbol changes. Higher depths indicate indirect or transitive dependencies with lower immediate risk.

Why does GitNexus say the index is stale?▼

A stale index means the repository graph no longer matches the current code. Run npx gitnexus analyze in the terminal to rebuild the index before running impact analysis again.

When should I not rely on impact analysis alone?▼

Impact analysis is based on static dependency confidence scores, so dynamic calls, reflection, or runtime wiring may be missed. Combine it with process flow reads and test coverage for critical paths like auth or payments.

Related Skills

Explore More Software Engineering Skills→
AlexiosBluffMaraAlexiosBluffMara
2

gitnexus-explorer

Index a codebase into a navigable knowledge graph with symbols, dependencies, and execution flows.

Community
Advanced
LonelyHerbivoreLonelyHerbivore
92

gitnexus-impact-analysis

Analyze upstream dependencies to reveal breakage from symbol changes.

Community
Intermediate
laozhong86laozhong86
1

gxpm-review-changes

Map diffs to affected symbols and execution flows for code review risk analysis.

Community
Advanced
PyModelPyModel
18

gitnexus-exploring

Explore codebase architecture and trace execution flows using GitNexus indexed repositories.

Official
Intermediate