docs-updater

# Universal Documentation Updater Analyzes git changes since the latest release tag and updates the documentation files that should change with them. ## Overview Use git history to identify release-relevant changes, then update `README.md`, `CHANGELOG.md`, and any relevant documentation folders. Keep the workflow focused on explicit user approval, precise edits, and repository-specific documentation structure. ## When to Use Use this skill when: - Preparing release notes or an `Unreleased` changelog update - Syncing `README.md` or documentation after feature work lands - Reviewing what changed since the last release before a PR or release ## Prerequisites Before starting, verify that the following conditions are met: ```bash # Verify we're in a git repository git rev-parse --git-dir # Check that git tags exist git tag --list | head -5 # Verify documentation files exist test -f README.md || echo "README.md not found" test -f CHANGELOG.md || echo "CHANGELOG.md not found" ``` If no tags exist, inform the user that this skill requires at least one release tag to compare against. ## Instructions ### Phase 1: Detect Last Release Version **Goal**: Identify the latest released version to compare against. **Actions:** 1. Detect the comparison baseline and display it: ```bash LATEST_TAG=$(git describe --tags --abbrev=0 2>/dev/null) if [ -z "$LATEST_TAG" ]; then echo "No git tags found. This skill requires at least one release tag." echo "Please create a relea...