Write release notes from merged pull requests
Merged PRs since the last release, grouped and written for users, saved as a draft GitHub release.
- You start it: When you start it
- Asks you first
What it does
The task
Open the repository repo on GitHub and list the pull requests merged since the tag last tag. Group them into new features, improvements, fixes and breaking changes, from their titles, labels and descriptions. Write one line per change in plain words for users, with the PR number. Leave out chores, tests and dependency updates that do not change behavior. Save the notes as a draft release for the tag new tag. Ask me before you publish it.
- It works in GitHub, in the workspace you pick, and signs in with passwords from your Cuiar vault.
- It runs once, when you start it.
- It stops for your approval before it sends, posts, pays, books or changes a record.
What you give it
| Blank | What to give | Example |
|---|---|---|
| repo | The GitHub repository | brightleaf/web |
| last tag | The tag of the last release | v2.4.2 |
| new tag | The tag of the new release | v2.5.0 |
What you get back
An example run with the example values above. Your run uses your own data.
Draft release v2.5.0: 31 PRs since v2.4.2
New
- Export invoices as XLSX. (#812)
- Set a default currency for each workspace. (#798)
Improved
- The dashboard loads 40% faster on large accounts. (#805)
Fixed
- Totals with 3 or more tax rates were rounded wrong. (#817)
Breaking
- API: /v1/reports returns dates in ISO 8601. (#801)
Left out: 22 chores, tests and dependency updates.
Saved as a draft. Waiting for your approval to publish.
Run it in Cuiar
- 01
Open it
Click Use in Cuiar on this page. The side panel opens with the task in the composer.
- 02
Fill in 3 blanks
Type repo, last tag and new tag. Tab moves to the next blank.
- 03
Run it
Run sends it to the agent. Follow each step in the panel, and stop it at any time.
From the terminal
cuiar exec "Open the repository brightleaf/web on GitHub and list the pull requests merged since the tag v2.4.2. Group them into new features, improvements, fixes and breaking changes, from their titles, labels and descriptions. Write one line per change in plain words for users, with the PR number. Leave out chores, tests and dependency updates that do not change behavior. Save the notes as a draft release for the tag v2.5.0. Ask me before you publish it."Run it from your AI agent
Claude Code, Codex, Cursor and other MCP clients reach Cuiar at https://mcp.cuiar.com/mcp. Add the server one time, then ask for the task in plain words, or call run_task yourself.
1. Add Cuiar to Claude Code
claude mcp add --transport http cuiar https://mcp.cuiar.com/mcp2. Ask your agent
Use the Cuiar tool run_task to run my "Write release notes from merged pull requests" template with repo = brightleaf/web; last tag = v2.4.2; new tag = v2.5.0.Setup for other agents: AI agents.
The tool call
{
"name": "run_task",
"arguments": {
"task": "Open the repository brightleaf/web on GitHub and list the pull requests merged since the tag v2.4.2. Group them into new features, improvements, fixes and breaking changes, from their titles, labels and descriptions. Write one line per change in plain words for users, with the PR number. Leave out chores, tests and dependency updates that do not change behavior. Save the notes as a draft release for the tag v2.5.0. Ask me before you publish it."
}
}Related templates
All engineering templatesEngineering
Read the changelogs before you upgrade dependencies
Breaking changes, security fixes and upgrade steps for each outdated package, from its release notes.
You start it: When you start it- GitHub
- npm
- PyPI
Engineering
Find flaky tests in your CI runs
Tests that fail and then pass on the same commit, with the count and the error, from your recent runs.
You start it: When you start it- GitHub
- Google Sheets
Engineering
Compare open-source libraries before you pick one
Downloads, releases, open issues, license and size of each library, with a recommendation.
You start it: When you start it- GitHub
- npm
- PyPI
Engineering
Write an incident postmortem from the timeline
A blameless draft with the timeline, impact, cause and actions, built from chat, monitors and deploys.
You start it: When you start it- SSlack
- Datadog
- GitHub
- +1 more: Google Docs
Engineering
Search for fixes to an error message
Known causes and fixes for your error from forums, issues and docs, ranked by how well they match.
You start it: When you start it- Stack Overflow
- GitHub
- Any forum
Engineering
Sort the security alerts in your repositories
Open Dependabot alerts across your repos, grouped by package, with the fix version and any open fix PR.
On a schedule: Every Monday at 9:30- GitHub