writing-changelogslisted

# Writing Changelogs Write changelog entries and release notes that humans actually want to read. This skill activates when writing changelog entries, preparing GitHub releases, or reviewing release notes quality. **Sources**: [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), [Common Changelog](https://github.com/vweevers/common-changelog) ## When to Use - Writing entries for `CHANGELOG.md` - Preparing GitHub release notes via `/system:release` - Reviewing changelog entries before release - Transforming commit messages into user-friendly descriptions ## Core Principles 1. **Changelogs are for humans, not machines** - Write for users, not developers 2. **Communicate impact, not implementation** - Focus on what users can DO, not what files changed 3. **Use imperative verbs** - "Add", "Fix", "Remove" not "Added", "Fixed", "Removed" 4. **Include references** - Link to commits, PRs, or issues when available 5. **Plain language over jargon** - Explain, don't assume knowledge ## Entry Format ### Basic Template ```markdown - [Imperative verb] [user benefit/what changed] ([reference]) ``` ### With Sub-details (for significant changes) ```markdown - **[Feature Name]** - [User benefit explanation] - [Technical detail 1] - [Technical detail 2] ``` ## Good vs Bad Examples | Bad (Developer-focused) | Good (User-focused) | | --------------------------------------------------- | ------------------