Fip
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.From its SKILL.md
npx -y skills add skatekowski/wheee-plugin --skill fipAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
FIP — Functionality Isolation Protocol
Analyze the dependency graph of a file or symbol to understand what a change will affect.
Process
- Identify the target (file path or symbol name from $ARGUMENTS)
- Find all files that import/require the target
- Find all files that the target imports/requires
- Map the dependency tree (2 levels deep)
- Identify protected zones (files that should NOT be modified)
- Report the FIP scope
Output Format
## 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
Rules
- Always check for circular dependencies
- Flag shared state (global variables, singletons, shared configs)
- Include test files that test the target
- Protected files: package.json, lock files, CI configs, shared types