code-generate-document

You can auto-generate inline docstrings for functions and classes by analyzing your codebase changes. The system adapts to specific file paths or code modifications to produce inline documentation directly within your source files.

Generating an Architecture Decision Record (ADR) for design choices involves analyzing code changes and formatting the architectural context into a standardized document. The output is written to standard locations such as the doc/adr/ directory.

Yes, you can generate module-level documentation and update README files. By analyzing specified arguments or code modifications, the system produces top-level explanations for modules and writes the results to standard documentation locations.

Generating documentation for a codebase handles specific files or paths by adapting to provided arguments or detected code changes. It focuses the documentation generation process on the targeted locations rather than the entire project.

You do not need external code review tools to format generated ADRs, as the system integrates with convention-reviewer and code-architect components. These integrations handle output formatting and ensure the results meet architectural standards.

You should use ADRs instead of inline docstrings when documenting high-level architectural design choices rather than individual function or class behaviors. ADRs capture the context and rationale behind structural decisions, while inline docs explain implementation details.