Write release notes from a list of changes
Paste commit messages or merged pull request titles and get release notes people outside the team can read.
New · Be one of the first to try it
What you'll get
- Notes grouped by New, Improved, Fixed
- One plain sentence per change
- Internal-only changes left out
- Unclear items flagged for a human
Fill in the blanks
Stays on your device. We never see what you type here.
Use it
You can fill in the blanks first, or just go: the AI will ask you for them.
How it went for other people
Nobody has used this one yet. You could be the first, and your answer will show up here.
About the creator
Riprova TeamOfficial
Starter prompts from the people who run Riprova. Rated by you, not by us.
36 prompts · See their page
Advanced
Exact numbers
- Said it worked
- Not enough answers
- Answers
- 0 (0 yes, 0 partly, 0 no)
- Uses
- 0
Answers from people and automatic tracking are always counted separately. The creator's own uses are not counted.
Raw instructions
Turn these changes into release notes for this audience: {{audience}}.
Changes: {{changes}}
Group them under "New", "Improved", "Fixed" and, only if any exist, "Breaking changes" at the top. Write each item as one sentence about what the reader can now do or what no longer goes wrong, not what the code does. Drop internal-only changes (dependency bumps, refactors, CI) unless they affect the reader. Keep the same facts; do not add features that are not in the list. If a change is ambiguous, put it under a final "Need a human to check" list with the original wording, rather than guessing.Blanks: {{changes}}, {{audience}}
Use with your AI tool
- Download SKILL.md for Claude Code, Cursor and other agent tools.
- Use with your AI tool automatically (MCP): your tool fetches workflows itself and reports whether they worked.
Version history
- Version 2Sep 25, 2026Updated from the seed filecurrent
- Version 1Sep 23, 2026First version
Something wrong with this prompt? Report a problem