impact-analysis

Trace direct and indirect dependencies of a target file or symbol.

3|Updated Mar 19, 2026

Search Tags:#imports #grep #static-analysis #blast-radius #impact-analysis #code-dependencies #test-mapping

Ready to run

npx skills add https://github.com/t6adev/claude-code-tools --skill impact-analysis-t6adev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: impact-analysis
Source: https://github.com/t6adev/claude-code-tools/tree/main/tools/skills/code/impact-analysis
Command: npx skills add https://github.com/t6adev/claude-code-tools --skill impact-analysis-t6adev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

impact-analysis helps you map out the ripple effects of code changes by tracing imports and references from a starting target to identify directly and indirectly affected files and tests.

Core Features & Use Cases

Direct dependency tracing: identify modules that directly import or reference the target.
Indirect dependency tracing: resolve up to two levels of dependencies to gauge blast radius.
Test mapping: locate affected test files to validate changes.
Safe analysis notes: ignores dynamic imports and external packages, and highlights potential gaps.

Quick Start

Analyze the impact of changing a target file or symbol by providing a file path or symbol name.

Frequently Asked Questions about impact-analysis

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

FAQPage Schema

How do I map the blast radius of code changes to find affected files?▼

To map the blast radius of code changes, trace direct and indirect dependencies starting from a target file or symbol. This static analysis identifies affected modules and tests up to two dependency levels deep.

What is static dependency tracing and how does it identify affected tests?▼

Static dependency tracing locates files that import or reference a target module. By resolving these references up to two levels deep, it maps the ripple effects and highlights test files needed to validate the changes.

How do I find which modules import a shared utility or public API?▼

You can find modules importing a shared utility or public API by running static analysis on the target file path or symbol name. The tool enumerates direct importers and resolves indirect dependencies to gauge the full impact.

Does static impact analysis work with dynamic imports and external packages?▼

Static impact analysis ignores dynamic imports and external packages, focusing exclusively on internal project references. It excludes node_modules and flags these potential gaps to ensure safe and predictable analysis.

What is the best way to trace code dependencies for a specific symbol?▼

The best way to trace code dependencies for a specific symbol is using static reference analysis. Provide the symbol name to enumerate direct and indirect importers, mapping the blast radius up to two dependency levels.

Can I use static analysis to map code dependencies for large projects?▼

You can use static analysis to map code dependencies for large projects by tracing imports from a target file. It resolves up to two dependency levels, though dynamic imports and external packages are ignored to maintain accuracy.