Keep a Changelog Generator — Standards Without Busywork

Generate changelog entries that follow a consistent, readable structure without spending hours formatting by hand.

Still formatting changelogs manually every release?

Standards are useful, but formatting overhead slows teams down

Tedious and repetitive

Scrolling through dozens of commits, opening PRs, and summarizing each change takes 30+ minutes per release.

Inconsistent formatting

Different team members write notes in different styles. One release reads like documentation, the next like a git log dump.

Too developer-focused

Raw commit messages mention internal modules, ticket numbers, and refactors your users don't care about.

Easy to skip entirely

When writing notes is painful, releases ship with "bug fixes and improvements" — or no notes at all.

From raw commits to clean versioned entries

Get structured changelogs faster with better readability

BeforeRaw commits
migrate user table to new schema
wip: search (broken)
search working now
fix typo in onboarding email
perf: lazy-load settings panel
bump eslint to v9
AfterGenerated changelog

Added

  • Search: Find what you need instantly with the new search feature.

Changed

  • Performance: The settings panel now loads faster with lazy-loading.

Fixed

  • Onboarding Email: Corrected a typo in the welcome email.

WIP commits, dependency bumps, and internal refactors are filtered out automatically.
No commit conventions required — write however you like.

Manual Keep a Changelog vs Changesmith

AreaManualChangesmith
Entry categorizationManual sorting each releaseAuto-grouped draft entries
Drafting qualityDepends on writer availabilityConsistent user-facing phrasing
Commit format dependenceHigh cleanup burdenHandles mixed commit styles
Time per releaseOften hoursOften minutes

Why teams use a Keep a Changelog generator

Consistency, clarity, and less release-day formatting

Ship releases in minutes, not hours

Generate draft release notes the moment you tag a version. Review, tweak, and publish — done.

Write notes users actually read

AI rewrites developer-speak into plain language. Your customers see what changed for them, not internal implementation details.

Keep every release consistent

Changesmith matches your existing changelog style so every version looks like it was written by the same person.

Filter out the noise automatically

Dependency bumps, WIP commits, and CI config changes are excluded so release notes only surface meaningful changes.

Stay in control with editing

AI generates the draft — you have the final say. Edit with a side-by-side markdown editor before publishing.

No commit convention required

Forget enforcing prefixes across your team. Changesmith understands plain-language commits just as well as conventional ones.

Three-step changelog workflow

Select range, generate draft, publish final notes

1

Install the GitHub App

One click to connect your repository. Changesmith only requests the permissions it needs — read access to commits and PRs, write access for releases.

2

Pick a tag range

Select the start and end tags for your release. Changesmith collects all commits in that range and sends them to the AI for analysis.

3

Review and publish

Edit the generated changelog in a live markdown editor, then publish directly to GitHub Releases with one click.

Built for developers who ship

Your source code is never stored

Changesmith reads commit metadata only. Code stays in your repository.

Data never used for AI training

Your commit data is processed, not collected. Nothing is used to train models.

Revoke access anytime

Uninstall the GitHub App and all access is immediately removed.

Changesmith is a solo project built by Philip Ludington, an indie game developer who got tired of writing release notes by hand. What started as a side project became a tool used by developers who value their time as much as their code.

Keep a Changelog Generator FAQ

What is Keep a Changelog format?

Keep a Changelog is a widely used structure for release notes with clear categories like Added, Changed, Fixed, and Removed for each version.

How does Changesmith help with Keep a Changelog?

Changesmith analyzes commit and PR history, drafts user-facing entries, and organizes output in a changelog-friendly structure that teams can quickly finalize.

Do I still need to manually sort entries?

Usually much less. Changesmith handles initial grouping and wording so manual cleanup is significantly reduced.

Can I edit generated content before publishing?

Yes. You can review and edit all generated entries in markdown before publishing.

Does this require strict commit prefixes?

No. Changesmith works with mixed and imperfect commit histories.

Can I use this with GitHub releases?

Yes. You can publish final output to GitHub releases after editing.

Related pages: Changelog Software · Release Notes Template · Git Changelog Generator

Ready to generate cleaner changelogs faster?

Use Changesmith to produce standards-aligned release notes in minutes.

Try Changesmith Free