From wheee
Functionality Isolation Protocol — analyze dependencies for a file or symbol to understand the blast radius of changes. Use when running 'fip', 'dependency analysis', 'impact analysis', or before refactoring.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wheee:fiphaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze the dependency graph of a file or symbol to understand what a change will affect.
Analyze the dependency graph of a file or symbol to understand what a change will affect.
## FIP Analysis: [target]
### Direct Dependencies (imports)
- [file] — imports [symbol]
### Reverse Dependencies (imported by)
- [file] — uses [symbol]
### FIP Scope (safe to modify)
- [file 1]
- [file 2]
### Protected (DO NOT modify)
- [file] — [reason: external API, shared config, etc.]
### Blast Radius
- X files in scope
- Y files protected
- Risk level: LOW / MEDIUM / HIGH
npx claudepluginhub skatekowski/wheee-plugin --plugin wheeeAnalyzes blast radius of file or function changes by mapping direct and transitive dependents with lenskit_graph or grep on import patterns.
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.
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.