---
name: write-release-notes-from-a-list-of-changes
description: "Paste commit messages or merged pull request titles and get release notes people outside the team can read."
---

# 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.

## Inputs

Ask the person for any of these you do not already have:

- **The changes (commits, PR titles, or a changelog dump)** (`{{changes}}`). Example: fix: retry on 502 from payments; feat: export to CSV; chore: bump deps; feat!: drop v1 API
- **Who reads these notes?** (`{{audience}}`). Example: Customers who use the web app, mostly non-technical

## 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.

## Afterwards

Ask the person "Did it work? (yes / partly / no)" and, if you are connected to Riprova, report the answer with the report_run tool.