← Gallery

Write release notes from commits

Turns the commits since the last tag into release notes people can read: new features, fixes and anything that needs action when upgrading.

Kind
Recipe
By
Plexiform (@CallumJB125) self-declared
License
CC0-1.0
Added
2026-10-10
Updated
2026-10-10
Stacks
any
Tools
auto
Tags
release, git
sha256
e22d2de18dc864485ce184767cd7a043ce4db218a8e5e5e68a5d174ec6c692d4

Turns the commits since the last tag into release notes people can read: new features, fixes and anything that needs action when upgrading.

Read-only: it plans and reports, and never changes files. Cost: Low: reads commit messages and a few diffs.

The prompt

Write release notes for the changes since the last release.

1. Find the latest tag with `git describe --tags --abbrev=0` (if there is none, use the first commit) and list commits since then with `git log <tag>..HEAD --no-merges`.
2. Sort them into: New, Improved, Fixed, and Breaking changes or action needed. Leave out internal chores, test-only and CI-only changes.
3. Write each item as one sentence a user would understand, not the commit message.
4. Suggest the next version number (semantic versioning) and say why.

Output Markdown only. Do not change any files or create tags.

To add it: in Plexiform, open Discover in the sidebar, then Add. You see everything it contains before anything is saved.