Skip to content
Skills Library
Programming · Analysis

impact-analyzer

/impact-analyzer

Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.

Repository
SourceAtlas ↗
Licence
MIT
Last repository change
21.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.

Triggers from the description

what will break if I change Ximpact of changing Xdependencies of Xis it safe to modify X
Original author description

Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.

How it works

  1. When to Use
  2. Instructions
  3. Target Formats
  4. What User Gets
  5. Example Triggers
Original SKILL.md headings · 40 lines, 171 words
SKILL.md preview
---
name: impact-analyzer
description: Analyze what code will be affected by changes. Use when user asks "what will break if I change X", "impact of changing X", "dependencies of X", "is it safe to modify X", or before making significant code changes.
---

# 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

1. Identify the file, component, or API the user wants to change
2. Run `/sourceatlas:impact "<target>"` with the target
3. 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"

Versions

The database has no other skills named impact-analyzer.

Database snapshot: 13.11.2026 · package version 226300d1babc (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100impact
    This skill should be used when the user asks to "analyze impact of changes", "check blast radius", "what would break if I change this", "refactoring safety analysis", or mentions keywords related to change impact assessment and dependency tracing.
  • 100gitnexus-impact-analysis
    Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\
  • 100gitnexus-impact-analysis
    Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\
  • 100code-documentation-analyzer
    Analyze code documentation analyzer operations. Auto-activating skill for Technical Documentation. Triggers on: code documentation analyzer, code documentation analyzer Part of the Technical Documentation skill category. Use when analyzing or auditing code documentation…
  • 100impact-map
    Use when the user asks for a map of their project, what depends on what, what would be affected or break if they change or delete something, or what permissions they have given Claude Code ("خريطة الأثر", "شو بيتأثر لو حذفت", "impact map", "what breaks if"). Builds a local HTML…
  • 100anvien-impact-analysis
    Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: \"Is it safe to change X?\", \"What depends on this?\", \"What will break?\

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.