Release note generator
Group commits or task bullets into Added, Changed, Fixed, and Notes.
Inputs stay in your browser. feat goes to Added, fix to Fixed, change/refactor to Changed, and chore, docs, or other prefixes to Notes.
How to use this tool
Group commits or task bullets into Added, Changed, Fixed, and Notes.
Transform raw Git commit logs into polished, structured release notes and changelogs. Automatically groups conventional commits into Features, Bug Fixes, Performance, and Documentation sections.
💡 3 Quick Steps to Get Started
Paste recent git commit lines from your repository history.
The tool parses conventional prefixes (feat:, fix:, docs:, perf:) into organized categories.
Copy clean, release-ready Markdown changelogs directly into GitHub Releases or update blogs.
When it helps
Useful for product updates, customer notes, and internal handoff.
How it works
feat goes to Added, fix to Fixed, change/refactor to Changed, and chore, docs, or other prefixes to Notes.
Worked example
Example: convert feat, fix, change, and chore lines into release notes.
Limits and data handling
Treat the Markdown as a draft and verify names, version, and user impact before publishing.
No. Lines are grouped in the browser and analytics records only the tool identifier.
Semantic Versioning (SemVer), Changelog & Release Notes Guide
1. Semantic Versioning (SemVer 2.0.0) Architecture
SemVer dictates a three-part `MAJOR.MINOR.PATCH` numbering convention. MAJOR releases increment upon breaking API alterations, MINOR releases denote backward-compatible feature additions, and PATCH increments address non-breaking bug fixes.
2. The Keep a Changelog Standardized Categorization
Changelogs designed under the Keep a Changelog specification structure updates across standard categories: Added, Changed, Deprecated, Removed, Fixed, and Security.
3. Technical Changelogs vs. User-Facing Product Notes
Engineering changelogs detail commit hashes and internal refactors, whereas user-facing release notes translate technical achievements into tangible user benefits and operational walkthroughs.
Feedback
How can we improve this tool?
Send a suggestion or bug report for this tool.
FAQ
What can I enter in the Release note generator?
Enter one commit or task per line. Common prefixes such as feat, fix, and chore are recognized.
How does the Release note generator choose sections?
feat goes to Added, fix to Fixed, and change or refactor to Changed; chore, docs, and every other prefix go to Notes.
Can I publish the Release note generator result unchanged?
Treat the Markdown as a draft and verify names, version, and user impact before publishing.
Does the Release note generator upload commit messages?
No. Lines are grouped in the browser and analytics records only the tool identifier.