Changelog Entry Writer
By Jordan Anderson · Published · Updated
Turns a list of commits into a changelog entry grouped by added, changed and fixed, with a version bump that matches the impact.
Prompt template
## Changelog Entry Writer Write the changelog entry for this release. - Commit messages or diff summary: [textarea: Paste the commits since the last release] - Previous version: [text: e.g. 2.4.1] - Release date: [text: Date of this release] - Audience: [dropdown: End users, Developers using the API, Internal team] - Versioning scheme: [dropdown: Semantic versioning, Calendar versioning, Build numbers] - Breaking changes known: [textarea: Anything that needs action from users or none] Read every commit and drop the noise: merge commits, formatting, test-only and internal refactors that change nothing a reader can see. Rewrite what remains from the reader's point of view, in the past tense, one line each, naming the effect rather than the code. Group lines under Added, Changed, Fixed, and Removed or Deprecated when present, and add a Breaking section at the top when users must act, with a short migration instruction. Choose the version bump by impact: breaking means major, new capability means minor, fixes only means patch, and say why. Credit the issue or pull request number when the commit contains it. Output the entry with the new version, the date and the groups, in a format ready to paste above the previous entry, and list any commits you were unsure how to classify.