doc-maintenance

To keep documentation in sync with code, this Skill audits recent commits against README, SPEC, and PRODUCT files to detect drift. It then proposes minimal edits and opens a pull request with the suggested changes.

Yes, you can automatically fix documentation drift after major feature merges. The Skill operates on demand or on a periodic schedule, creating a feature branch and opening a PR with non-destructive edits to align your docs.

The best way to audit top-level project documents is to compare recent repository commits against target files like README, doc/SPEC.md, and doc/PRODUCT.md. This process aggregates a precise change summary for reviewer approval.

No, the documentation update process does not rewrite your files. It proposes minimal, non-destructive edits to restore accuracy, ensuring your README and SPEC documents remain structurally intact while fixing drift.

You can schedule periodic documentation audits by running the Skill on a recurring basis. It will automatically scan for drift between your code and docs, then create a branch and open a PR with the necessary alignment changes.

Documentation drift occurs when recent code commits modify features without corresponding updates to README, SPEC, or PRODUCT files. This Skill identifies those discrepancies and proposes minimal edits to restore accuracy.