changelog
turn merged changes into release notes a customer can read
Reads what merged since the last release and keeps what a user would notice, grouped as breaking, added, changed and fixed. Each line says what the product does now.
structure generate skill changelogSkill — changelog
Invoke in any agent conversation with /changelog. The steps below are a starting opinion, and
they are what runs — edit them until they describe the notes this company would want to receive.
When to use. At every release, and before any announcement that claims something is new.
Steps.
- Take the range — the last release to now — and read what merged in it.
- Keep what a user would notice. Refactors, dependency bumps and internal moves stay out unless behavior changed.
- Group into breaking, added, changed, fixed. Breaking goes first, always, with what to do about it.
- One line per entry, written as what the product does now — not as what the commit did.
- Link each entry to the change, and put the version and the date at the top.
- Read the first three lines as someone who has been away a month. If they cannot tell whether to upgrade, rewrite them.
---
type: skill
name: changelog
description: turn merged changes into release notes a customer can read
standing: draft
owner: "{{owner}}"
updated: "{{date}}"
---
# Skill — changelog
_Invoke in any agent conversation with `/changelog`. The steps below are a starting opinion, and
they are what runs — edit them until they describe the notes this company would want to receive._
**When to use.** At every release, and before any announcement that claims something is new.
**Steps.**
1. Take the range — the last release to now — and read what merged in it.
2. Keep what a user would notice. Refactors, dependency bumps and internal moves stay out unless
behavior changed.
3. Group into breaking, added, changed, fixed. Breaking goes first, always, with what to do about
it.
4. One line per entry, written as what the product does now — not as what the commit did.
5. Link each entry to the change, and put the version and the date at the top.
6. Read the first three lines as someone who has been away a month. If they cannot tell whether to
upgrade, rewrite them.
type: skill
name: changelog
about: "Reads what merged since the last release and keeps what a user would notice, grouped as breaking, added, changed and fixed. Each line says what the product does now."
version: "0.1.0"