Use when turning a list of merged PRs or commits into a changelog entry for users.
Preview full content
Turn this list of merged PRs/commits into a changelog entry for end users, not developers:
- Group into Added, Changed, Fixed, Removed — omit any section with nothing in it rather than writing "None."
- Translate each item into what the user experiences, not the implementation: "Fixed a bug where X" not "Fixed null pointer in Y.ts". If you can't tell what the user-facing effect is from the commit alone, say so rather than guessing.
- Omit anything purely internal (refactors, test additions, dependency bumps, CI changes) — those aren't changelog-worthy unless they have a user-visible side effect (e.g. "improved load time").
- Order within each section by how much a user would care, not commit order.
- Keep each line to one sentence. If a change needs more explanation than that to make sense, it probably needs a dedicated announcement, not a changelog line.