When should I run the /impact command?

You should run it before refactoring core logic, changing shared types, deleting exports, or modifying API signatures to understand potential breaking changes.

How does this skill identify code dependents?

The skill uses Grep and Glob tools to search for imports, function calls, and type references across your entire repository to map the dependency chain.

Can I use it on uncommitted work?

Absolutely. If no specific file or function is provided as input, the skill will automatically analyze your current uncommitted changes.

Does it automatically check test coverage?

Yes, it identifies existing unit and integration tests related to the modified code and flags which tests may require updates due to your changes.

What is Impact Analysis in Claude Code?

It is a specialized skill that scans your codebase to identify all files, functions, and tests affected by a proposed code change before you commit.

System Impact Analysis

Name: System Impact Analysis
Author: hereinthehive

byhereinthehive

開発者ツール

Analyzes system-wide ripple effects of code changes to prevent regressions and breaking changes in shared components.

概要

This skill empowers developers to perform proactive impact analysis before modifying shared utilities, refactoring core functionality, or changing API signatures. By searching for direct dependents, tracing downstream effects, and identifying relevant test coverage, it provides a comprehensive risk assessment that prevents surprise breakages in unrelated parts of the codebase. It transforms 'blind' changes into informed migrations, ensuring that every modification is accounted for across the entire system through detailed reports and actionable recommendations.

主な機能

Automated dependency tracing for shared utilities and types
Actionable coordination reports for synchronized file updates
Assessment of unit and integration test coverage for planned changes
0 GitHub stars
Identification of impacted API routes and downstream UI components
Detailed risk level categorization (Low, Medium, High) for every change

ユースケース

Preparing for a major version update or changing public API signatures
Modifying a shared TypeScript interface or database schema with wide-ranging dependencies
Refactoring a core utility function or shared library used across multiple modules

概要

主な機能

Automated dependency tracing for shared utilities and types
Actionable coordination reports for synchronized file updates
Assessment of unit and integration test coverage for planned changes
0 GitHub stars
Identification of impacted API routes and downstream UI components
Detailed risk level categorization (Low, Medium, High) for every change

ユースケース

Preparing for a major version update or changing public API signatures
Modifying a shared TypeScript interface or database schema with wide-ranging dependencies
Refactoring a core utility function or shared library used across multiple modules