What problem does it solve? Teams often treat changelogs as raw git log dumps or skip them entirely, leaving users unable to understand what changed between releases. This Skill enforces the Keep a Changelog 1.1.0 format so every release gets a clear, human-readable, linkable entry. ## Core Features & Use Cases - Structured Release Entries: Enforces the six change categories (Added, Changed, Deprecated, Removed, Fixed, Security) in the correct order, with version/date headers and reverse-chronological ordering. - Unreleased Section Workflow: Manages the [Unreleased] section at the top of the file, renaming it to the new version and date at release time. - Comparison Links & Yanked Releases: Adds per-version diff links for GitHub/GitLab and marks pulled releases with a machine-parseable [YANKED] tag. - Use Case: When preparing a v1.4.2 release, ask the AI to convert the accumulated Unreleased entries into a properly formatted ## [1.4.2] - 2026-03-14 section with categorized changes and a fresh comparison link. ## Quick Start Use the keepachangelog skill to add a new release entry for version 1.4.2 to my CHANGELOG.md based on the changes currently listed under Unreleased.