code-module

Generate a tree-structured module overview by triggering the init-modules command, which builds a hierarchical directory tree and produces a modules.md file containing concise function summaries for each directory in your codebase.

The best way is to use an automated leaf-to-root propagation workflow that creates a structural skeleton, populates descriptions incrementally, and validates coverage to ensure every directory has a meaningful description in markdown.

Yes, you can create a markdown tree view for large projects by generating a hierarchical modules.md document that provides per-directory summaries and validates complete coverage across the entire codebase structure.

Leaf-to-root propagation works by generating concise summaries for leaf directories first, then incrementally propagating these descriptions upward to parent directories to build a complete hierarchical overview.

Generating a module overview requires no external dependencies, allowing you to directly analyze your codebase structure and output a tree-structured markdown document with directory-level summaries.

You should avoid using automated tree-structure documentation if your project lacks distinct functional modules, as the validation process enforces meaningful descriptions for every single directory in the codebase.