Changelogs Are Boring to Write. Still Gotta Do Them.
You’ve just shipped version 2.1.0. There are fourteen commits, three bug fixes, a new feature, and a deprecated endpoint. Now you need to write it all up in a format that doesn’t look like you copied the git log and called it a day.
The Changelog Generator takes your raw list of changes (or straight-up git log output) and organizes them into a properly formatted changelog. It supports both Keep a Changelog and Conventional Commits format, automatically sorting entries into Added, Changed, Fixed, Deprecated, Removed, and Security categories. You plug in the version number, and it handles the structure.
The output is a solid first draft. You’ll probably want to reword a few entries to be clearer for end users (commit messages and user-facing release notes aren’t the same thing), but the categorization and formatting save you the tedious part.
What It Does
- Supports Keep a Changelog and Conventional Commits — the two formats most open-source projects use
- Automatically groups entries by type: Added, Changed, Fixed, Deprecated, Removed, Security
- Adds version number and release date headers
- Accepts raw git log output as input, so you can paste directly from your terminal
- Produces clean, copy-ready markdown
Quick Walkthrough
- Enter the version number (e.g., 2.1.0)
- Pick your format — Keep a Changelog or Conventional Commits
- Paste your changes or git log
- Click “Generate Changelog”
Feed it something like “added dark mode, fixed login bug on mobile, updated API response format, removed deprecated v1 endpoints” and you’ll get a structured changelog with each entry under the right category header, properly formatted with the version and date.
Why Bother With a Proper Changelog
Grouping changes by type lets users quickly scan for what matters to them. Someone upgrading your library cares about breaking changes and deprecations. A product manager wants to see new features. A security team needs to know about patches. A wall of unsorted commit messages doesn’t serve any of them well.
Recognized formats like Keep a Changelog also make your project look maintained and professional. Contributors are more likely to engage with projects that clearly communicate what’s changing.
Where This Gets Used
- Every release cycle — instead of spending twenty minutes formatting, spend two
- Open-source projects where a CHANGELOG.md is expected by the community
- Sprint retrospectives where you need a structured summary of completed work
- Package publishing on npm, PyPI, or crates.io where release notes accompany version bumps
- Internal tools where stakeholders want to know what changed without reading pull requests
The README Generator creates project documentation to complement your changelog. The Bug Report Generator structures issue reports for your tracker.
Questions
Can I just paste my git log?
Yes. Paste the raw commit messages and the AI will sort them into the right categories. It won’t be perfect — commit messages like “fix stuff” don’t give it much to work with — but well-written commits produce well-organized changelogs.
Which format should I use?
Keep a Changelog is more human-readable and widely adopted for public projects. Conventional Commits is more structured and integrates with automation tools. Pick whichever matches your team’s conventions.
Do I really need a CHANGELOG.md?
If other people use your software, yes. It’s how users decide whether to upgrade, what broke, and what they’re getting. It takes five minutes per release with this tool.
Cost?
Free, and you never have to make an account.