impact

Analyze direct and transitive dependents of a source file across a codebase.

71|7|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/mbwsims/claude-universe --skill impact-mbwsims
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impact
Source: https://github.com/mbwsims/claude-universe/tree/main/skills/impact
Command: npx skills add https://github.com/mbwsims/claude-universe --skill impact-mbwsims

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before modifying code, developers need to know what will break, which files depend on a target, and whether tests protect those dependents; this Skill surfaces the blast radius so changes can be planned safely.

Core Features & Use Cases

  • Dependency discovery: Locate direct and transitive dependents of a target file using a dependency graph or grep-based fallbacks.
  • Import-level risk annotation: Distinguish value imports from type-only imports and annotate importer risk accordingly.
  • Test and coverage checks: Find direct tests and tests that import the target, flagging untested or under-tested dependents.
  • Cycle detection and guidance: Identify circular dependency cycles and recommend refactors or mitigations.
  • Use case: Before renaming or changing a function signature in a shared module, run the Skill to enumerate importers, check which imports are type-only, find related tests, and produce a prioritized risk assessment.

Quick Start

Run /impact with the path to the file you plan to change to get a dependency graph, importer details, and a test coverage risk summary.

Frequently Asked Questions about impact

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

FAQPage Schema
How do I analyze the blast radius of changing a source file in my codebase?

To assess code change risk, traverse the dependency graph up to three levels to locate direct and transitive dependents of the target file. The analysis distinguishes value imports from type-only imports and flags untested dependents.

How do I find which files and tests depend on a shared module before refactoring?

Finding dependents involves scanning the dependency graph or using grep-based fallbacks to locate importers. The process identifies direct tests, flags under-tested dependents, and annotates importer risk based on whether imports are type-only or value imports.

Can I detect circular dependency cycles when evaluating import usage?

Yes, cycle detection identifies circular dependency cycles during impact analysis. It surfaces these cycles and recommends refactors or mitigations to help you safely plan code or API changes without cascading breaks.

Does impact analysis work for evaluating API signature changes across a repository?

Yes, impact analysis applies to source repositories when evaluating direct and transitive dependents before making API changes. It produces a prioritized risk assessment by checking import usage and relevant test coverage for the target file.

What is the best way to check test coverage risk for a module's dependents?

Checking test coverage risk involves finding direct tests and tests that import the target module. The analysis flags untested or under-tested dependents and surfaces per-export test coverage to help you prioritize changes safely.