doc-consistency-check

Documentation consistency checks analyze your project files to verify that all modules have corresponding, up-to-date references. This validates completeness, resolves duplicates, and ensures correctness across your project before marking a task complete.

Broken module dependency links occur when documentation lacks bidirectional references. A link consistency check validates that module dependencies are correctly referenced in both directions to prevent broken links.

Validating Mermaid diagram syntax requires a diagram validation check to ensure diagrams are syntactically correct and complete. This prevents rendering failures and ensures structural accuracy in your project documentation.

Yes, documentation consistency checks require access to project source code and documentation files. This access allows the tool to compare modified modules against existing docs and verify name consistency across all files.

Detecting duplicate documentation is best handled by an automated duplicate document detection process. It identifies and resolves redundant documentation for source files by analyzing project documentation consistency.

Verifying current dates and task numbers is performed through a dedicated date and task check. This confirms that all updated files within your project contain accurate timestamps and tracking numbers for version control.