gitnexus-impact-analysis

Map dependency blast radius for changed code symbols with confidence scores.

9|9|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill gitnexus-impact-analysis-nullmastermind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gitnexus-impact-analysis
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/gitnexus/gitnexus-impact-analysis
Command: npx skills add https://github.com/nullmastermind/viber-router --skill gitnexus-impact-analysis-nullmastermind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and reviewers determine what will break or be affected when changing code by mapping symbol-level dependencies and execution flows to assess risk before editing or committing changes.

Core Features & Use Cases

  • Dependency Blast Radius: Identify direct and transitive dependents of a target symbol with confidence scores and depth levels (d=1, d=2, d=3) so teams can prioritize testing and code review.
  • Pre-commit Change Detection: Map staged or uncommitted changes to affected processes and flows to flag high-risk edits before they reach the repository.
  • Risk Assessment & Reporting: Summarize impact as LOW/MEDIUM/HIGH/CRITICAL based on affected symbols, processes, and whether the change touches critical paths like auth or payments.
  • Use Case: Before refactoring validateUser, run an impact analysis to list WILL BREAK direct callers, identify affected login and token flows, and decide whether to gate the change behind tests or a rollout.

Quick Start

Run an impact analysis for the symbol validateUser, list d=1 direct callers and processes that will break, and provide a concise risk level and recommended mitigation.

Frequently Asked Questions about gitnexus-impact-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is code change blast radius analysis and how does it work?

Blast radius analysis maps direct and transitive dependents of a changed code symbol with confidence scores and depth levels to surface affected processes and callers. It produces a risk summary to prioritize tests and gate commits.

How do I check the impact of staged code changes before committing?

Run a pre-commit impact analysis to map staged or uncommitted changes to affected processes and execution flows. This flags high-risk edits and generates a risk summary before changes reach the repository.

Can I assess repository-wide risk for refactoring a specific function?

Yes, repository-wide impact assessment identifies direct and transitive dependents of a target symbol across the codebase. It annotates depth levels and confidence scores to validate refactoring safety and prioritize review.

Does dependency analysis evaluate risk for critical paths like authentication?

Yes, risk assessment summarizes impact as LOW, MEDIUM, HIGH, or CRITICAL based on affected symbols and processes. It evaluates whether changes touch critical paths like auth or payments to recommend mitigations.

What are the limitations of depth-limited dependency analysis?

Depth-limited dependency analysis maps dependents at specified depths like d=1, d=2, and d=3. While it provides confidence-scored dependents and process-level risk summaries, deep transitive impacts beyond the configured depth limit may remain unmapped.