impact
Analyze system-wide impact of changes before making them. Use before modifying shared utilities, changing APIs, or refactoring core functionality.
npx skills add majiayu000/claude-skill-registry --skill impact --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Impact Analysis Analyze the system-wide impact of proposed or recent changes before you make them. ## Philosophy Code doesn't exist in isolation. A "small fix" in a shared utility can break ten components. A type change can cascade through the entire codebase. > "What else depends on this? What might break?" This skill isn't about being cautious—it's about being **informed**. Make changes with full knowledge of their ripple effects. ## When to Use Run `/impact` before: - Modifying shared utilities or types - Changing API signatures - Refactoring core functionality - Deleting or renaming exports - Making changes that "seem small but might ripple" ## Input The user will provide: - File path(s) being changed, OR - Function/class/type name being modified, OR - Description of planned change If nothing provided, analyze uncommitted changes. ## Process ### 1. Identify Change Scope Determine what's being modified: - File(s) affected - Exports being changed (functions, types, classes) - API signatures being modified - Data structures being altered ### 2. Find Direct Dependents Search for code that directly uses the modified code: - Files that import from the changed file - Functions/compo
- Philosophy
- When to Use
- Input
- Process
- 1. Identify Change Scope
- 2. Find Direct Dependents
- 3. Check Test Coverage
- 4. Trace Downstream Effects
- Output Format
- Why This Matters
What does the impact skill do?
Analyze system-wide impact of changes before making them. Use before modifying shared utilities, changing APIs, or refactoring core functionality.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill impact --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.