Agent skill · Writing

Release notes writer

Turns merged pull requests or a commit log into release notes people want to read: groups changes into new, improved, fixed and breaking, drops internal-only work, describes what users can now do rather than how it was built, and gives migration steps for anything breaking. Offers a short social version too. Use when asked for release notes, a changelog entry or a summary of what shipped.

The release-notes-writer/ folder with SKILL.md.

The skill itself. Agents read the name and description first and load the rest only when a task matches.

release-notes-writer/SKILL.md
---
name: release-notes-writer
description: "Turns merged pull requests or a commit log into release notes people want to read: groups changes into new, improved, fixed and breaking, drops internal-only work, describes what users can now do rather than how it was built, and gives migration steps for anything breaking. Offers a short social version too. Use when asked for release notes, a changelog entry or a summary of what shipped."
---

# Release notes writer

Write notes for the people who use the product, from what the team merged.

## Steps

1. Get the changes: PR titles and descriptions, or the commit log since the last release (`git log <last-tag>..HEAD --merges --oneline` in a repo). Note the version and date if given.
2. Sort each change into New, Improved, Fixed, Breaking or Internal. Internal covers refactors, CI, dependency bumps with no visible effect, and test-only changes.
3. Drop Internal from the notes. List what you dropped at the end so someone can check.
4. Rewrite each kept change as one line about the user: what they can now do, or what no longer goes wrong. Link the PR number if the notes are public and the repo is.
5. For each Breaking change write: what changed, who is affected, and the exact steps to migrate, with before and after code if it's an API.
6. Put the most important change first, in a one-sentence summary at the top.
7. Write a short version under 280 characters for social or chat, with the one change most people will care about.

## Rules

- Never describe a change you can't trace to a PR or commit. If a title is unclear, say "unclear: #123" rather than guess.
- No internal names (ticket IDs, codenames, people) in public notes.
- Present tense, plain words: "Export now includes tags", not "Implemented tag serialization in the export pipeline".
- Keep breaking changes even if there's only one, and put them before Fixed.

## Example

```
## 2.4.0 (2026-11-19)
CSV export now includes tags and custom fields.
### New
- Export prompts with their tags and custom fields (#412)
### Fixed
- Saving a prompt with an emoji in the title no longer fails (#418)
```