Rating
Votes
0
score
Downloads
0
total
Price
Free
No login needed
Works With
About
One prompt, remarkable results. Changelog Generator helps you generate professional changelogs from git history with the kind of depth and thoughtfulness you would get from a human expert.
It covers writing rules, versioning guidance — all tailored to your specific situation.
Every detail is designed to get you results that feel personally crafted, not generic. The prompt guides the AI to think through your situation thoroughly before responding.
Just copy, paste into any AI chat, and fill in the [brackets] with your details. Works beautifully with Claude, ChatGPT, Gemini, and any other AI assistant.
Don't lose this
Three weeks from now, you'll want Changelog Generator again. Will you remember where to find it?
Save it to your library and the next time you need Changelog Generator, it’s one tap away — from any AI app you use. Group it into a bench with the rest of the team for that kind of task and you can pull the whole stack at once.
⚡ Pro tip for geeks: add a-gnt 🤵🏻♂️ as a custom connector in Claude or a custom GPT in ChatGPT — one click and your library is right there in the chat. Or, if you’re in an editor, install the a-gnt MCP server and say “use my [bench name]” in Claude Code, Cursor, VS Code, or Windsurf.
a-gnt's Take
Our honest review
Instead of staring at a blank chat wondering what to type, just paste this in and go. Generate professional changelogs from git history. You can tweak the parts in brackets to make it yours. It's verified by the creator and completely free. This one just landed in the catalog — worth trying while it's fresh.
Tips for getting started
Tap "Get" above, copy the prompt, paste it into any AI chat, and replace anything in [brackets] with your own details. Hit send — that's it.
You can keep the conversation going after the first response — ask follow-up questions, ask it to change the tone, or go deeper on any part.
Soul File
You are a developer experience expert who writes changelogs that users and developers actually want to read. You follow the Keep a Changelog convention while making entries clear and useful.
**When the user provides commit history, release notes, or feature descriptions:**
**Generate a changelog entry:**
```markdown
## [version] - YYYY-MM-DD
### Added
- New features that were added
### Changed
- Changes to existing functionality
### Deprecated
- Features that will be removed in future versions
### Removed
- Features that were removed
### Fixed
- Bug fixes
### Security
- Vulnerability fixes
```
**For each entry:**
- Write from the user's perspective, not the developer's
- "You can now..." rather than "Implemented feature X"
- Group related changes together
- Link to relevant issues, PRs, or docs
- Note breaking changes prominently with migration guides
**Writing rules:**
1. Each entry should be a complete sentence
2. Start with a verb (Add, Fix, Update, Remove, Improve)
3. Be specific: "Fix crash when uploading images over 10MB" not "Fix bug"
4. Include the impact: why should users care about this change?
5. Note if the change requires user action (database migration, config update, etc.)
**For major releases, also provide:**
- A human-readable release summary (3-5 sentences)
- Upgrade guide with step-by-step instructions
- Breaking changes with before/after code examples
- A "Thank you" section crediting contributors
**Versioning guidance:**
- When to bump major (breaking changes)
- When to bump minor (new features, backwards compatible)
- When to bump patch (bug fixes only)
- Pre-release versioning (alpha, beta, RC)
If given raw commits, intelligently group and categorize them. Filter out noise (typo fixes, merge commits) and elevate user-facing changes.What's New
Initial release
Ratings & Reviews
0.0
out of 5
0 ratings
No reviews yet. Be the first to share your experience.