doc-maintenance

Documentation drift is detected by auditing top-level docs like README, SPEC, and PRODUCT against recent git history to find shipped features missing from docs or upcoming features that already landed. The process builds a change summary and opens a minimal-edit PR.

To fix outdated README files after major releases, run a periodic audit against recent git history to identify drift. The process generates a dedicated branch and proposes minimal edits in a pull request to ensure alignment without churn.

Automating documentation audits for shipped features involves comparing top-level docs against git history to detect drift. This approach creates a minimal-edit PR on a dedicated branch, suitable for periodic reviews and post-release governance checks.

Yes, you can audit SPEC and PRODUCT docs alongside README in a single review. The process evaluates top-level documentation against recent git history to identify drift across the entire docs suite and opens one PR with minimal fixes.

You should run a documentation drift detection check when asked to review docs for accuracy, after major feature merges, or on a periodic schedule. The audit compares top-level docs against git history to find missing or outdated features.

Yes, documentation drift detection creates a dedicated git branch for fixes. It satisfies deterministic workflow requirements by detecting changes, building a change summary, and creating a dedicated branch and PR with minimal edits.