docs-updater

This skill automates documentation maintenance by analyzing the git changes between the current branch and the most recent release tag, then proposing updates to the files that should change with them. It solves the recurring release chore of keeping README.md and CHANGELOG.md in sync with what actually shipped, following the Keep a Changelog standard and conventional-commit semantics to categorize changes into Added, Changed, Fixed, Removed, and Security sections.

The workflow runs in phases: verify the git repository and that release tags exist, detect the latest release version, perform diff analysis (commit counts, file statistics, commit messages, add/modify/delete status), discover documentation structure by scanning for docs folders and standard files, generate categorized changelog entries, and update README and documentation folders. Critically, it presents a summary of proposed changes and requires explicit user confirmation via AskUserQuestion before applying any edits. It declares only Read, Edit, and Bash tools, and the Bash usage is limited to read-only git inspection commands (git describe, git log, git diff, git rev-list) plus filesystem existence checks.

It targets maintainers and developers preparing a release, syncing docs after feature work lands, or reviewing what changed before opening a pull request. Because it edits documentation files in place, it modifies the working tree, but it does so only after presenting a review and getting approval, and it never pushes, deletes source code, or runs destructive commands.