Use case · Engineering

Write release notes from what actually merged

To write release notes with AI agents, connect GitHub and your issue tracker, such as Linear or Jira, to a Brainwrite bot. It reads the pull requests merged since the last release and the issues they closed, groups the changes, and drafts two versions: plain-language notes for customers and a technical changelog for the team. You review both before anything is published or posted.

Download for Mac See the ready-made team

Release notes from merged work

Read the pull requests merged into main since the v2.8.0 tag and the Linear issues they closed. Draft customer release notes in plain language, grouped into new, improved, and fixed, and a technical changelog for the team. Leave out internal refactors from the customer notes. Do not create the release or post anything.

Your Chief of Staff put a team on it

Atlas· Change collector
Sage· Release writer

31 pull requests merged since v2.8.0; 22 customer-facing, 9 internal
New: export reports to CSV; Improved: search is faster on large workspaces
Fixed: 8 issues, each linked to its Linear issue
Unclear: 2 pull requests have no description; listed for the author to explain

DoneSaved as a routine: Fridays at 15:00. It starts paused until you turn it on.

An illustrated example. Your team works on your own files and apps.

Split scene: at 11:04 pm a developer rubs his eyes alone at his desk; at 7:04 am he drinks coffee while AI agents Atlas and Dash show finished work.

The job

Doing it yourself, and handing it off.

Doing it yourself

Release day arrives and someone has to explain what changed. They scroll through forty merged pull requests with titles like fix edge case, open each one to work out what it means for a customer, and check which issues it closed. Internal changes get mixed in with features, and the notes go out either too technical or too vague. Sometimes they do not go out at all.

What the team does

List pull requests merged since the last release and the issues they closed
Group changes into new, improved, and fixed
Write customer notes in plain language and a technical changelog
Draft the Slack announcement for the release

What waits for you

What customers are told, and how
When the release is published
Whether and where the announcement is posted

The team

Who's on it.

Your Chief of Staff picks the specialists the job needs. Each has its own role, instructions, model, and app access.

AtlasIllustrated example
Change collector
Lists pull requests merged since the last release, reads their descriptions and linked issues, and drops internal-only changes from the customer list.
SageIllustrated example
Release writer
Drafts customer notes in plain language and a technical changelog, grouped into new, improved, and fixed.

How it runs

A run, step by step.

01
Connect the repos
Connect GitHub and Linear or Jira. Grant read tools; publishing a release is a separate step you approve.
02
Collect the changes
The collector lists merged pull requests since the last release tag and the issues they closed.
03
Draft both versions
The writer drafts customer notes and a changelog, and lists anything it could not explain.
04
Review and publish
You edit the notes, then publish the release and approve the Slack announcement.

Start faster

Ready-made teams for this job.

Add a team from the library in one click. You see a preview first; routines arrive paused and connected apps stay off until you approve them.

Team libraryShip Software SafelyView the team →

What you'll connect

Apps this job uses.

FAQ

Questions about Release notes from merged work

Can it create the GitHub release itself?

The GitHub connector can create a release and generate release notes, so a bot with those tools could do it. For this job, grant read tools and draft the notes first. Once you have reviewed them, publish the release yourself or approve the bot's request in the conversation.

What if a pull request has no description?

The collector reads the title, the changed files, the commits, and any linked issue. If it still cannot tell what a change means for a customer, it lists the pull request as unclear instead of guessing, so the author can explain it in a sentence.

Does it work with GitLab or Bitbucket?

Yes. The GitLab connector lists merge requests with their commits and discussions, and the Bitbucket connector lists pull requests with their commits. Jira and Linear both supply the issues. The same draft-then-review approach applies to all of them.

Built on