analyze-module

To generate module documentation, you can analyze the repository module to automatically produce a structured write-up covering responsibilities, class structures, file mapping, and dependency tracing. This replaces manual tracing by extracting core call chains and design rationale directly from the code.

Tracing data flow for refactoring involves mapping upstream and downstream dependencies alongside core call chains. By analyzing the module, you can identify transformation steps and protocol pipelines to ensure the refactoring updates preserve the original architectural intent.

Yes, module analysis supports detailed architectural reviews across core call chains, protocol pipelines, and transport layers. It evaluates module responsibilities and design rationale to clarify where the module sits within the broader system architecture.

When documentation is outdated, you trigger a module analysis to regenerate the write-up. This process enumerates key classes, methods, source files, and headers, clarifying exactly what the module does and does not do within the architecture.

Yes, the module analysis specifically supports the Prism framework. You can ask it to analyze the desired Prism module, specify the depth and output path, and it will produce the full module design documentation.

You should avoid automated module documentation when a repository module lacks coherent trigger-based structures or when the core call chains are too fragmented to trace. It requires readable source files and headers to accurately map dependencies and design rationale.