Use casesReporting

Release notes written from the pull requests you already merged

Mitra writes your release notes from the week's merged pull requests. Every Thursday at 5pm the agent reads what landed in GitHub and groups it into features, fixes and chores. The page is published to Notion, the highlights go to Slack, and every run is recorded.

Runs: Thursdays at 5pm
Used by: Engineering · Product Managers

The prompt

Each Thursday at 5pm, write release notes from the pull requests merged this week, split into features, fixes and chores. Publish to Notion and post highlights to #product.

GitHub

Notion

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

Collect the merged work
The agent lists every pull request merged since the last run, with its title, description and labels.
Sort into three groups
Each change lands in exactly one group, using labels where they exist and the description where they do not.
Write it in plain language
Every line says what changed for the person using the product, not which branch it came from.
Publish the page
The notes go into your Notion releases database as a new dated page, in the format your team uses.
Post the highlights
The three or four changes worth knowing about go to the channel, with a link to the full page.

Make it yours.

For whoever writes release notes on Thursday evening by scrolling the merge history and hoping nothing was missed. Change any of this by saying so — there is nothing to rewire.

Publish to a draft page and wait for approval before it goes out.
Run twice a month, covering everything merged since the last release.
Add the ticket number beside each line, for teams tracking against Linear.

Questions, answered.

Can release notes be generated from GitHub pull requests?

Yes. Mitra reads your merged pull requests and writes the notes from their titles, descriptions and labels. Anything vague in a pull request stays vague in the notes, so the output is only as good as your habits, and you can edit the Notion page afterwards.

How do I keep release notes readable for people who don't read code?

Tell Mitra who the notes are for and the agent writes in that register: one plain line per change, no branch names, and no ticket numbers unless you ask for them. Internal-only work can be dropped, or pushed into a short chore list at the bottom.