document-reviewer

To check documentation accuracy after a codebase refactor, audit project docs and README files to identify inconsistencies and verify references align with the current code and architecture, generating an actionable remediation plan.

Ensuring consistency across markdown documentation involves reviewing committed docs to surface inconsistencies, verifying that code references match the current implementation, and enforcing alignment with architecture and release requirements.

You need to review project documentation for gaps after code changes, refactors, or before releases to ensure accuracy against the current codebase, internal consistency, and writing quality across all project references.

Yes, you can use git committed docs to audit project documentation quality by reviewing the latest committed files after a code change to surface inconsistencies and verify alignment with the current codebase architecture.

Documentation review works for README files and code references by assessing accuracy against code and architecture, ensuring consistency across all project documents, and providing a concise remediation plan for identified issues.

Automated documentation consistency checks focus on verifying accuracy against code and alignment with architecture, but limitations include requiring committed markdown docs to review and needing manual execution of the generated remediation plan.