doc-review

To audit markdown documentation, you can run a command to spawn a doc-maintainer agent that scans all project Markdown files for drift, broken links, and outdated references. It checks correctness and freshness, then autonomously applies fixes within its authority.

Documentation drift occurs when project docs fall out of sync with the codebase during refactors or feature launches. You need to run a doc audit before releases to ensure all markdown files reflect current code, verifying completeness, freshness, and link validity.

Yes, you can autonomously fix project documentation issues during a release cycle. The doc-maintainer agent applies approved fixes directly to your markdown files, reducing drift and providing a report of changes and required approvals.

Yes, the doc audit works with existing markdown documentation without extra dependencies. It requires no external components and directly loads all project markdown docs to scan for correctness, completeness, and consistency across refactors.

The best way to maintain documentation freshness is to run an autonomous doc audit before major feature launches. This ensures all markdown references stay aligned with the codebase by scanning for drift and applying fixes within authority.

Project documentation often gets broken links after a codebase refactor due to documentation drift. Running a comprehensive markdown audit detects these outdated references and autonomously fixes them to ensure docs stay aligned with code.