Prompt · Developer Tools

Changelog Writer

Turns raw commit history into a changelog humans actually want to read.

Have ready: Paste the commits since the last release

Fill in · 5 fields

PASTE git log --oneline OR THE COMMIT LISTNEW VERSION NUMBERDATEEND USERS / DEVELOPERS / BOTHNEEDS CLARIFICATION

Your prompt

Write a changelog entry from these commits.

Commits since last release:
[PASTE git log --oneline OR THE COMMIT LIST]
Version: [NEW VERSION NUMBER]
Release date: [DATE]
Audience: [END USERS / DEVELOPERS / BOTH]

Rules:
1. Group under: Breaking Changes, Features, Fixes, Performance, Docs/Chore (omit empty groups).
2. Rewrite each entry in user-facing language, what changed for the READER, not what the diff did. Merge trivial commits; drop pure refactors unless user-visible.
3. Breaking changes get a MIGRATION note with before/after code.
4. Credit contributors by handle if present in the log.
5. Add an upgrade-risk line: who should upgrade immediately vs who can wait.

Keep it scannable. If a commit message is too vague to describe accurately, mark it [NEEDS CLARIFICATION] instead of inventing details.

Paste it into Muse or any assistant. Blank fields stay as [brackets].

More like this