[NTTP]

Changelog & Release Notes Writer

Paste a rough list of what shipped. Get a clean changelog entry, grouped and translated for the right audience.

Rough notes or a bullet list, however messy. One item per line works well.

Optional

Optional. Shown as the header on the entry.

Free to try, no sign-up needed

Your text isn't stored. It's sent to Anthropic to generate your result, then discarded. Privacy

Prefer to write it yourself? Use the free prompt.

New to this? Read the guide.

What it produces

Real output from this tool, not a mock-up.

What went in

What shipped
fixed the thing where exports over 50k rows silently truncated instead of emailing a link. added the multi site report, one report covers all sites with per site breakdown. sped up dashboard load, was 4s now about 900ms. fixed a bug where the date picker jumped to 1970 if you cleared it. added CSV as an export format alongside JSON. removed the old v1 API endpoints that were deprecated in March.
Who this is for
Users
Version number or date
v3.4.0, 12 August 2026

What came back

v3.4.0, 12 August 2026 New - Added a multi site report that covers all your sites in one place, with a per site breakdown. - You can now export to CSV, in addition to JSON. Improved - Dashboards now load in about 900ms, down from around 4 seconds. - Exports over 50,000 rows now email you a download link instead of silently cutting off at 50,000 rows. Fixed - Fixed a bug where clearing the date picker would jump it to 1970. Removed - Removed the old v1 API endpoints that were deprecated back in March.

When to use it

Use this to turn a rough list of what shipped into release notes someone will actually read. Who it is for changes everything: users need to know what is different for them, developers need the breaking changes, and the same commit list reads differently for each.

Common questions

Can I paste raw commit messages?
Yes, and rough notes work just as well. Commit messages describe the change; a changelog has to describe the difference, which is why pasting the git log directly makes such poor release notes.
What does the audience setting change?
A lot. Users want what is different and what they should do about it, with the internal detail removed. Developers need breaking changes and deprecations called out clearly. Internal notes can keep the caveats and the known issues you would not publish.
Should I include bug fixes nobody reported?
Usually yes, briefly. A silent fix that changes behaviour is exactly what generates a confused support ticket later. The truncated export in the example is worth a line precisely because people may have relied on the broken behaviour without knowing.
Is it free?
You can run it three times a day with no account. Signing in gives you renewing monthly credits, and this tool costs one credit per run with the one-click refinements included.

Similar tools

All Founders

Project Brief Builder

Turn a rough idea into a clear, decision-ready brief: the problem, the users, the MVP scope, and what is out.

FoundersSign in

App Name Generator

Describe what you're building. Get distinctive, ownable name ideas across styles, vetted, with what to check before you commit.

FoundersFree to try

Launch Post Writer

Describe what you shipped. Get an X thread, a brand-account post, a LinkedIn post, and a portfolio blurb in an honest builder voice.

FoundersSign in

Elevator Pitch & One-Liner Writer

The spoken version of what you do, for when someone asks out loud. Not website copy, a one-sentence and a 30-second version you can actually say. (For homepage messaging, see Value Proposition & Tagline Writer.)

FoundersFree to try