Use casesReporting

Release notes written from the pull requests you already merged

Mitra can write your release notes from the week's merged pull requests: every Thursday at 5pm, an agent reads what landed in GitHub, groups it into features, fixes and chores, publishes the page to Notion, and posts the highlights to Slack. Every run is recorded step by step.

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

The prompt

Each Thursday at 5pm, read every pull request merged in our repos since last Thursday, write release notes that separate features from fixes and chores, publish them as a new page in Notion, and share the three biggest items in #product.

GitHub

Notion

Slack

Build this agent

200 credits to start · no credit card

What the agent actually does.

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

Make it yours.

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

Publish to a draft page and wait for a human to approve the wording before it goes out.
Run twice a month instead of weekly, covering everything merged since the last release.
Add the ticket number beside each line, for teams that track releases against Linear.

Questions, answered.

Can release notes be generated from GitHub pull requests?

Yes — Mitra builds an agent that 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. 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, no ticket numbers unless you ask for them. Internal-only work can be dropped, or pushed into a short chore list at the bottom.