doc-maintenance

Documentation drift is detected by comparing current top-level docs against recent git history. This audit surfaces inaccuracies in your README, SPEC, and PRODUCT files by analyzing recent commits and identifying where documentation no longer matches the codebase.

The best way to automate minimal fact-based edits is by running a doc audit workflow that builds concise change summaries. It creates a feature branch, applies non-disruptive factual edits to align docs with code, and generates a PR containing only the necessary fixes.

Yes, you can generate a PR for documentation updates directly from your git workflow. The audit process builds concise change summaries from recent commits, creates a feature branch, applies minimal edits to your docs, and opens a pull request containing the factual fixes.

A doc review cursor maintains a running baseline by updating its position after changes are applied. This tracking mechanism records progress across cycles, allowing future documentation audits to compare current docs against the correct historical commit baseline.

Yes, the documentation audit workflow explicitly supports SPEC and PRODUCT files alongside the README. It identifies drift across all three top-level documentation files and proposes minimal, fact-based edits to bring them back into alignment with recent commits.