skills.rest
truongnat
truongnatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

gitnexus-impact-analysis

Identify direct and transitive dependents of code targets before refactoring.

Updated Mar 5, 2026
Search Tags:#impact analysis#dependency mapping#git diff#GitNexus#refactoring safety#pre-commit review#code risk assessment
One-click install
npx skills add https://github.com/truongnat/emplus --skill gitnexus-impact-analysis-truongnat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/truongnat/emplus/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis
Command: npx skills add https://github.com/truongnat/emplus --skill gitnexus-impact-analysis-truongnat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky code changes by predicting what will break and which execution paths depend on the thing you plan to modify, so you can refactor or patch with confidence.

Core Features & Use Cases

  • Upstream dependency impact: Finds direct callers/importers (depth d=1) and broader transitive effects (depth d=2–d=3) for a given symbol or target.
  • Git-change blast radius: Maps staged or current git changes to affected flows to estimate risk before committing.
  • Process-aware verification: Reads affected execution flows from GitNexus processes to confirm what will be impacted, not just what looks related.
  • Use Case: If you plan to change a core validation function, it will help you identify which login/token/session paths will be impacted so you can update tests or safeguards.

Quick Start

Ask the AI to run an upstream impact analysis for validateUser and report the risk level and affected dependents.

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 the blast radius of a git diff before committing?▼

To check the blast radius of a git diff, you map staged changes to affected execution paths using impact analysis. This identifies direct dependents and transitive risks to prevent risky modifications.

What is upstream dependency impact analysis?▼

Upstream dependency impact analysis identifies direct callers and broader transitive effects up to depth d=3 for a given symbol. It predicts what will break before refactoring so you can patch with confidence.

How do I find what will break if I modify a core validation function?▼

To find what will break when modifying a core validation function, run an upstream impact analysis. It identifies affected login, token, and session paths so you can update tests or safeguards before refactoring.

Can I assess code risk using confidence thresholds for a refactoring task?▼

Yes, you can assess code risk for refactoring using confidence thresholds. The analysis calculates dependency depth from d=1 to d=3 and evaluates risk levels to map affected execution flows and dependents.

Does impact analysis work with staged git changes to map execution flows?▼

Yes, impact analysis works with staged git changes to map affected execution flows. It reads process flows from GitNexus to confirm what will be impacted, verifying risks beyond just visually related code.

When do I need to run a pre-commit code risk assessment?▼

You need to run a pre-commit code risk assessment before refactoring or patching code. It maps the upstream blast radius of your changes to identify transitive risks and prevent breaking dependent execution paths.

Related Skills

Explore More Software Engineering Skills→
wutongshenqiuwutongshenqiu

gitnexus-refactoring

Map code symbol dependents to determine refactoring blast radius.

Community
Advanced
Chai-UnChai-Un

fix

Fix lint errors and formatting issues using yarn, prettier, and linc.

Community
Intermediate
TimMoyenceTimMoyence

gitnexus-impact-analysis

Identify code change blast radius by analyzing dependents and execution flows.

Community
Intermediate
ConavaConava
2

kb-blast-radius

Compute reverse dependencies from seed changes to identify impacted files.

Community
Intermediate