From codebase-pilot
Analyzes the blast radius of a file change — finds all dependents, transitive imports, affected tests, and risk score. Best before modifying shared files like types, utilities, or core modules.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codebase-pilot:impact-analysisThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Trace the impact of changing any file across the codebase.
Trace the impact of changing any file across the codebase.
codebase-pilot impact --file <path>
codebase-pilot impact --file src/types.ts
Output:
Risk: HIGH (53/100)
Direct dependents (18):
src/agents/generator.ts
src/mcp/server.ts
...
Affected tests (5):
tests/agents/generator.test.ts
tests/cli/pack.test.ts
...
Total affected: 27 files
--prune for pack: codebase-pilot pack --compress --prune <file> packs only reachable fileshttp://localhost:7456/impact?file=<path>npx claudepluginhub kalpeshgamit/codebase-pilot --plugin codebase-pilotAnalyzes blast radius of file or function changes by mapping direct and transitive dependents with lenskit_graph or grep on import patterns.
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.
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.