# Release Notes

> Helps write notes about changes.

- Skill: `jeromeetienne/release-notes` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jeromeetienne/release-notes`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jeromeetienne/release-notes/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: jeromeetienne (https://skillmd.com/u/jeromeetienne)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/jeromeetienne/release-notes

---


# Release notes

Write release notes for the people who use the product.

1. Find the two versions. If the user does not give them, use the last two git tags.
2. Read the commits and the merged pull requests between the two versions.
3. Put each change in one of three groups: New, Changed, Fixed.
4. Write each change as one sentence that a user can understand. Do not write internal names, file paths, or commit hashes.
5. Leave out the changes that a user cannot see, such as refactoring and changes to tests.
6. Start with the version number and the release date.