Skill

impact-analyzer

Analyzes impact of changes to files, APIs, components, or models. Provides dependency analysis, risk assessment, breaking changes, migration checklist, and test coverage gaps before modifications.

code-quality

npx claudepluginhub lis186/sourceatlas --plugin sourceatlas

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Trigger this skill when the user:

SKILL.md

Similar Skills

impact

Analyzes blast radius, risk level, direct/indirect dependents, tests, and reviewers before file changes. Use for production code, refactoring, or paths like payment/auth/billing/security.

2 files

claude-impl-tools

impact

Analyzes blast radius of file or function changes by mapping direct and transitive dependents with lenskit_graph or grep on import patterns.

6 tools

universe

cs-impact

Analyzes impact of changing a function by listing direct callers, affected files, dependencies, and risk assessment. Useful when refactoring or assessing code changes.

codescope

Stats

Parent Repo Stars33

Parent Repo Forks1

Last CommitDec 23, 2025

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Impact Analyzer

When to Use

Trigger this skill when the user:

Is about to modify code and wants to know the impact

Asks what depends on a file or component

Wants to understand breaking change risks

Asks "what will break if I change X"

Asks "is it safe to modify this"

Instructions

Identify the file, component, or API the user wants to change

Run /sourceatlas:impact "<target>" with the target

Returns dependency analysis, risk assessment, and migration checklist

Target Formats

File path: /sourceatlas:impact "src/api/users.ts"

API endpoint: /sourceatlas:impact "api /api/users/{id}"

Component: /sourceatlas:impact "UserService"

Model: /sourceatlas:impact "User model"

What User Gets

Impact summary (backend, frontend, test files affected)

Risk level assessment (red/yellow/green)

Breaking change risks

Migration checklist

Test coverage gaps

Example Triggers

"What happens if I change this file?"

"What depends on UserService?"

"Is it safe to modify the authentication module?"

"Impact of changing the User model"

Impact Analyzer

When to Use

Trigger this skill when the user:

Is about to modify code and wants to know the impact
Asks what depends on a file or component
Wants to understand breaking change risks
Asks "what will break if I change X"
Asks "is it safe to modify this"

Instructions

Identify the file, component, or API the user wants to change
Run /sourceatlas:impact "<target>" with the target
Returns dependency analysis, risk assessment, and migration checklist

Target Formats

File path: /sourceatlas:impact "src/api/users.ts"
API endpoint: /sourceatlas:impact "api /api/users/{id}"
Component: /sourceatlas:impact "UserService"
Model: /sourceatlas:impact "User model"

What User Gets

Impact summary (backend, frontend, test files affected)
Risk level assessment (red/yellow/green)
Breaking change risks
Migration checklist
Test coverage gaps

Example Triggers

"What happens if I change this file?"
"What depends on UserService?"
"Is it safe to modify the authentication module?"
"Impact of changing the User model"