doc-maintenance

To automate documentation updates, the skill reviews your git history to detect new features and breaking changes, then proposes minimal edits to your README and SPEC files. It automatically creates a branch and opens a pull request for your review.

Yes, you can check your README for accuracy against recent GitHub commits. The skill analyzes your recent commit history to identify structural codebase changes, compares them against your top-level documentation, and flags areas where documentation drift has occurred.

The best way to prevent documentation drift after merging major features is to run an automated review process. This skill detects newly added features in your codebase, proposes necessary documentation updates, and generates a GitHub pull request to keep your docs synchronized.

Yes, you need a GitHub repository to automatically generate documentation pull requests. The skill requires both git and GitHub for version control operations, specifically to create a new branch, commit the proposed documentation edits, and open a pull request for review.

Automated documentation maintenance checks README, SPEC, and PRODUCT documentation files for accuracy. It cross-references the content within these specific top-level files against your recent git history to identify any missing features or breaking changes that need to be documented.

You should run automated documentation reviews after major feature merges or on a periodic schedule. Running the review process at these specific intervals ensures your top-level documentation consistently reflects the latest structural codebase changes without accumulating manual update backlogs.