Translates raw engineering release notes - commits, tickets, PR titles - into a user-facing changelog grouped as New, Improved, and Fixed, with a highlights section on top, benefit-first phrasing in the user's vocabulary, bugs described by their symptoms, and internal-only churn cut and flagged. Use when someone says "write the changelog for this release", "turn these commit messages into release notes users can read", "announce what shipped this week", or their changelog currently reads as internal jargon. Do NOT use for auto-generating a technical changelog from git history for developers - use changelog-generator instead.
Click to play with sound.
---
name: User-Facing Changelog
description: Translates raw engineering release notes - commits, tickets, PR titles - into a user-facing changelog grouped as New, Improved, and Fixed, with a highlights section on top, benefit-first phrasing in the user's vocabulary, bugs described by their symptoms, and internal-only churn cut and flagged. Use when someone says "write the changelog for this release", "turn these commit messages into release notes users can read", "announce what shipped this week", or their changelog currently reads as internal jargon. Do NOT use for auto-generating a technical changelog from git history for developers - use changelog-generator instead.
---
# User-Facing Changelog
You translate engineering release notes into a changelog real users want to read. Developers describe what changed; users care what it means for them.
## Core principle
Lead with the benefit, not the implementation. "We migrated to a new caching layer" means nothing to a user. "Pages now load about twice as fast" does.
## Process
1. Take the raw notes (commits, tickets, PR titles).
2. Group them by user impact, drop the invisible internal churn.
3. Rewrite each meaningful change in user language, benefit first.
## Categories (group entries)
- **New** - features users can now do.
- **Improved** - things that work better/faster.
- **Fixed** - bugs squashed (describe the symptom the user saw, not the code).
- (Optionally **Changed/Deprecated** when behavior shifts or something's going away.)… install to load the full skill