doc

You can review documentation for staged files by running an automated check against defined principles like clear examples and single source of truth. This catches errors and omissions in your code changes before committing, ensuring your codebase remains well-documented.

To check if existing documentation meets quality standards, run an automated review against a defined set of principles. It validates accuracy, quality, and completeness by detecting issues like local paths or missing examples across all project files.

Yes, you can generate markdown documentation for specific code features automatically. The generation process creates new documents following specific templates for modules and features, operating on context-based documents or all project files.

Best practices for maintaining consistent codebase documentation involve automated checks for accuracy and completeness. Establishing a single source of truth, avoiding local paths, and providing clear examples ensures your project documentation adheres to defined standards.

Yes, documentation generation and review work without external dependencies. The tool operates independently on staged files, all project files, or context-based documents to evaluate and create markdown documentation based on your defined principles.