build-dependency-graph

To generate a module-level dependency graph, this skill enumerates import and call relationships across source files, collapses file edges into module edges, and outputs structured YAML data alongside Mermaid-renderable Markdown diagrams.

Cycle detection for code dependencies works by identifying strongly connected components within the module-level graph, highlighting circular dependencies and high fan-in or fan-out modules that create maintainability risks.

Yes, you can visualize code imports as Mermaid diagrams because the skill automatically generates a Markdown file containing Mermaid-renderable module clusters and dependency edges suitable for architectural reviews and sharing.

Yes, dependency graph generation applies to projects spanning multiple languages and code organization styles by reading source files to extract imports regardless of the specific programming language used.

The best way to plan refactoring using a dependency graph is to leverage the generated structured YAML data to identify module hubs and cycles, enabling targeted impact analysis for architectural improvements.

When mapping codebase dependencies, you receive two output files: dependency-graph.yaml containing structured module edge data, and dependency-graph.md containing Mermaid diagrams and module clusters for review.