Stats
Actions
Tags
How this command is triggered — by the user, by Claude, or both
Slash command
/mindmap:impactThe summary Claude sees in its command listing — used to decide when to auto-load this command
Analyze the impact of changing a file or component in this project. **Requires a mind map with edges.** If `mindmap-output.json` has an empty `edges` array (which happens when `/mindmap:generate` only parsed at `summary` depth), tell the user to regenerate with `detailed` depth across source files before running impact analysis. Read `mindmap-output.json` and find the node(s) matching: $ARGUMENTS Trace the dependency graph to show: 1. **Direct dependents** (1-hop): files that import from the target 2. **Indirect dependents** (2-hop): files that depend on the direct dependents 3. **Risk l...
Analyze the impact of changing a file or component in this project.
Requires a mind map with edges. If mindmap-output.json has an empty edges array (which happens when /mindmap:generate only parsed at summary depth), tell the user to regenerate with detailed depth across source files before running impact analysis.
Read mindmap-output.json and find the node(s) matching: $ARGUMENTS
Trace the dependency graph to show:
Output a clear impact summary with risk assessment and suggested review/test actions.
If no mind map exists, tell the user to run /mindmap:generate first.
npx claudepluginhub engincankaya/claude-code-mind-map --plugin mindmap/impactPerforms cascade impact analysis on a file by reading module docstrings to show dependency chain of callers up to 3 levels, with exports, rules, and summary.
/impactFans out parallel agents to map the blast radius of a file, function, or directory before making changes — imports, tests, CI pipelines, docs, and code owners.