keep-a-changeloglisted

# Keep a Changelog Standard This skill provides comprehensive knowledge about the Keep a Changelog standard for writing human-readable changelogs. ## Core Principles 1. **Changelogs are for humans, not machines** - Write entries that help users understand what changed and why it matters to them 2. **Every version should have an entry** - Don't skip versions, even for minor releases 3. **Group changes by type** - Use consistent categories to organize changes 4. **Versions should be linkable** - Each version heading should be a link to a diff 5. **Latest version first** - Show the most recent changes at the top 6. **Show release dates** - Use ISO 8601 format (YYYY-MM-DD) ## Change Types (Sections) Use these sections in this order: - **Added** - New features - **Changed** - Changes in existing functionality - **Deprecated** - Soon-to-be removed features - **Removed** - Now removed features - **Fixed** - Bug fixes - **Security** - Vulnerability fixes Only include sections that have entries. Empty sections should be omitted. ## Version Format Versions follow Semantic Versioning (**MAJOR.MINOR.PATCH**, e.g., 1.2.3) — the SemVer impact rules and their mapping from commit types live in the `conventional-commits` skill. ## The Unreleased Section Always maintain an `[Unreleased]` section at the top: - Accumulates changes before the next release - Makes release preparation easier - Shows what's coming in the next version ## Writing Good Entries ### Do: - Start with a verb (