Changelog Generator
Generate polished, well-structured changelogs from raw commit messages, feature lists, or release notes — in any standard format.
Your Changelog Generator results will appear here
如何使用 Changelog Generator
- Paste your raw changes — commit messages, feature lists, Jira ticket summaries, or bullet-point notes from your sprint retrospective.
- Select a changelog format: 'Keep a Changelog' is the community standard, 'Conventional' follows the Conventional Commits spec.
- Enter the version number and release type to set the correct heading and context.
- Choose your audience — developer changelogs include technical details; end-user changelogs focus on benefits and impact.
使用案例
Generate a CHANGELOG.md entry from git log output before a release
Create user-facing release notes for a SaaS product update email
Produce dual-audience changelogs for open-source libraries (maintainers + users)
Compile sprint changes into a structured release summary for stakeholders
Document breaking changes with migration guides for major version bumps
最佳结果的技巧
- Paste raw git log output directly — the generator will categorize commits into Added/Changed/Fixed/Removed sections automatically.
- For breaking changes, include the old behavior and the new behavior in your input so the generator can write proper migration instructions.
- Use the 'Both' audience option for open-source projects where your changelog serves developers and non-technical users alike.
- Generate changelogs incrementally for each release rather than trying to cover multiple versions at once.
常见问题
What changelog format should I use?
Keep a Changelog (keepachangelog.com) is the most widely adopted standard for open-source projects. Conventional Changelog pairs well with Conventional Commits (feat:, fix:, etc.). Semantic Versioning Notes is best for libraries where version numbers carry strict meaning.
Can I paste git commit messages directly?
Yes. Paste the output of 'git log --oneline' or similar. The generator categorizes each commit into the correct changelog section (Added, Changed, Fixed, etc.) and rewrites terse commit messages into clear, descriptive changelog entries.
How does it handle breaking changes?
Breaking changes are flagged prominently at the top of the changelog with a BREAKING CHANGE prefix. If you provide details about the old and new behavior, the generator includes migration instructions to help users upgrade.
What is the difference between developer and end-user changelogs?
Developer changelogs include technical details: function names, API changes, dependency updates, and code examples. End-user changelogs translate the same changes into benefit statements: 'Pages now load 50% faster' instead of 'Migrated to React Server Components'.
Can I generate changelogs for pre-release versions?
Yes. Select 'Pre-release' as the release type and use a version like 3.0.0-beta.1. The generator will note the pre-release status and add appropriate disclaimers about API stability.
Part of these workflows
This tool is used in step-by-step guides that help you get more done
我们不存储您的文本。处理在实时进行，您的输入在生成结果后立即被丢弃。
解锁无限访问
免费用户：每天 5 次使用 | Pro 用户：无限制
See how this tool stacks up side-by-side:
✍️ Prompt Library
Ready-to-use prompts — click "Use This" to auto-fill the tool
Write a Python function that [describe what it does]. Include type hints and a docstring.
Explain this code and suggest improvements: [paste code]
Generate unit tests for the following function: [paste function]
Write a SQL query to [describe what you need] from a table with columns [list columns].
Create a README.md for a [project type] project with installation, usage, and contributing sections.