changelog-keeper

# Changelog Keeper ## Overview Keywords: changelog, CHANGELOG.md, Keep a Changelog, keepachangelog, semantic versioning, semver, release notes, version bump, Unreleased, changelog entry, release. This skill maintains a human-readable `CHANGELOG.md` following the [Keep a Changelog](https://keepachangelog.com) convention and [Semantic Versioning](https://semver.org). It writes entries that describe *what changed for users*, not raw commit messages, groups them under the six canonical change types, accumulates them under `## [Unreleased]`, and cuts dated, versioned releases when shipping. Use it to: start a new changelog, add an entry for a change, cut a release (move Unreleased to a dated version + bump the version number), draft release notes from a git diff/log, or audit/repair an existing changelog's structure. The six canonical groups (use these exact names, in this order): **Added · Changed · Deprecated · Removed · Fixed · Security** ## Workflow 1. **Locate or create the changelog.** Look for `CHANGELOG.md` at the repo root. If none exists, create one from `templates/CHANGELOG.template.md`. Never invent a parallel file (e.g. `changes.txt`). 2. **Classify the change** into exactly one of the six groups. Use the decision table below. If a change spans groups (e.g. removed a flag *and* added its replacement), write one entry per group. 3. **Write a user-facing entry.** Each entry is a single bullet, imperative or descriptive, focused on observable behavior. Translate...