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.
When & Why to Use This Skill
The Impact Analyzer is a specialized Claude skill designed to map code dependencies and predict the consequences of modifications. It enables developers to perform comprehensive impact analysis by identifying affected files, components, and APIs before code is even changed. This tool enhances software stability by providing risk assessments, migration checklists, and identifying potential breaking changes, making it an essential asset for safe refactoring and robust code maintenance.
Use Cases
- Safe Refactoring: Determine which parts of a large codebase will be affected when modifying shared components or core logic to prevent regression bugs.
- API Impact Assessment: Identify all frontend and backend dependencies before changing an API endpoint or data model to ensure compatibility.
- Risk-Based Testing: Use the impact summary and test coverage gaps to prioritize manual and automated testing efforts for high-risk changes.
- Documentation & PR Context: Automatically generate a detailed impact report and migration checklist to provide clear context for code reviewers in pull requests.
| 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
- 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"