On their own
- Read merged pull requests and issues
- Group changes by area
- Draft notes, summary and email
Marketing and content
Ship the feature and the announcement together.
A team reads what you merged this week, drops the internal-only work, and drafts release notes, a changelog entry and a short customer email. You publish.
Free and open source. macOS, Windows and Ubuntu.
Release notes
Every Thursday, read this week’s merged pull requests. Draft the changelog entry, a customer-facing summary and a short email. Leave out internal work. Publish nothing.
Your Chief of Staff put a team on it
- Tech Lead
- Copy
- Quality Gate
Release notes, this week
- 23 merged pull requests read
- 9 left out as internal work
- 14 changes grouped into 6 changelog entries
- Customer email drafted, 140 words
Waiting for your approval
Publish the changelog entry?
An example of the job. Your team works on your own work.
The team it puts on it.
Your Chief of Staff picks the specialists the job needs. Each one has its own role, instructions and engine.
Tech Lead
Reads the merged work and groups it by product area
Copy
Turns changes into benefits a customer understands
Quality Gate
Checks each claim against the merged changes
How it runs.
- Step 1Connect the repo, or pasteGitHub through connected apps, or paste the list of merged changes.
- Step 2Set the rulesWhat counts as internal, your changelog format, your tone.
- Step 3Three draftsChangelog, customer summary and email, each linked to the change it describes.
- Step 4You publishEdit and publish. Posting and sending stop and ask.
What the team does, and what waits for you.
Waits for you
- Publishing the changelog
- Sending the email
Start from a ready-made team.
From Murage’s library. Import one, look inside, and give it your brief.
Skills the ready-made teams load.
What the library teams above bring with them. Skill Guard scans each one.
- Community Led GrowthCommunity-led growth strategy advisor covering community platform selection, engagement frameworks, ambassador programs and community flywheel mechanics.
- Content Strategy EvaluationContent strategy assessment evaluating content quality, distribution effectiveness, audience alignment and production processes.
What you need.
What it takes to run this job. The Murage app is free; your AI provider bills you as usual.
- Murage and an AI engine (your existing Claude or ChatGPT plan, or an API key)
- GitHub through Flux Router credits or your own connected-apps key, or a pasted list of changes
- Murage open on your computer at run time. A run up to 12 hours late still happens
Rather have it set up for you?
We build your first release notes team with you, connect your tools and write your House Rules. Tell us what you need and we’ll quote before anything is booked.
Questions about release notes.
Will it invent features?
The Quality Gate bot checks each line against the merged changes you gave it, and House Rules tell every bot never to report a result it didn’t get. Read the draft before you publish it.
Can a coding engine help write it?
Yes. Give the writer bot Claude Code or Codex as its engine if you want it to read the code itself.
Release notes: hand it to a team tonight.
Give your first job to Murage.
Download the free app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for