Changelog Writing Prompt Builder

Turn commit noise into a changelog people actually read

A raw git log is written for machines and the engineer who wrote it — not for the people reading your release notes. This builder takes your commit messages or PR titles and produces a carefully structured prompt that an LLM can turn into a clean, grouped, benefit-focused changelog. Paste, configure, copy.

How it works

The tool parses each line you paste and embeds it in a prompt template with explicit instructions for the model: map conventional-commit prefixes to changelog headings (feat → Added, fix → Fixed, perf → Performance), drop non-user-facing noise like chore and ci, and rewrite every kept entry as a single benefit-led sentence. The prompt also pins the output to semantic versioning: breaking changes are pulled to the top, and the version heading and ISO date are formatted for you.

Choosing end-user vs technical audience swaps one instruction block. For users, the model translates jargon into outcomes (“faster load on slow connections”); for developers, it keeps the precise technical detail intact.

Tips for better changelogs

• Write conventional commits in the first place — feat:, fix:, perf: give the model unambiguous grouping signals.
• Squash trivial commits before pasting; one line per meaningful change keeps the changelog tight.
• Keep a ## Unreleased section in your repo and run this builder each release to clear it.
• If the model invents a feature, tighten the source commit message — the prompt already forbids inventing anything not implied by a commit.