Stats
Actions
Tags
From supp
Visualize file-level import/dependency graph — use when you need to understand what a module depends on or what depends on it. TRIGGER when: you need to understand file-level dependencies, what imports what, or assess blast radius of changing a module. DO NOT TRIGGER when: you need symbol-level dependencies (use /why) or just need to read file contents (use /ctx)
How this skill is triggered — by the user, by Claude, or both
Slash command
/supp:depsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the following command and show the user the output:
Run the following command and show the user the output:
supp deps --json $ARGUMENTS
-R for reverse deps)-d <N> to limit traversal depth for large projects--dot to generate Graphviz DOT output for visualization/why — it shows per-symbol deps, callers, and hierarchy/sym/ctx/tree/diff/deps src/main.rs — what files does main.rs depend on (tree view)/deps src/main.rs -R — what files depend on main.rs (reverse deps)/deps src/main.rs -d 1 — direct dependencies only, no transitive/deps --dot — whole-project graph in DOT format for Graphviz/deps — whole-project file dependency graphnpx claudepluginhub andrewpberg/supp --plugin suppGuides dependency graph exploration using CocoSearch for impact analysis, connection tracing, and hub identification.
Generates Mermaid flowcharts visualizing import dependencies between modules/packages/plugins. Detects circular dependencies, analyzes coupling, and assesses refactoring impacts.
Visualizes project dependency graphs across domains, detects circular dependencies, and analyzes cross-domain coupling in Python, JS/TS, and Go codebases. Use before refactoring, architecture reviews, or adding domains.