Automated changelog generation from merged PRs
Release notes write themselves from the week's merged pull requests.
Overview
On a release cadence, an agent reads the merged PRs since the last release, groups them into features/fixes/other, and drafts changelog copy in the product's voice.
How this workflow works
- Problem it solves
- Writing release notes is a manual, easily-skipped chore at the end of a sprint.
- Expected outcome
- A drafted changelog ready for a quick human edit, generated automatically on each release.
- Setup time
- 20 minutes
Steps
- 01Release cutA release branch or tag is created.
- 02Read merged PRsAn agent pulls PR titles and descriptions since the last release via the GitHub MCP server.
- 03Draft changelogChanges are grouped and rewritten in user-facing language.
Prerequisites
- GitHub MCP server
- Consistent PR title conventions
This workflow uses
More in Coding & Development
Reviews (4)
Solid, with a learning curve
Took about a week to tune the config to our repo's conventions, but once it clicked it's been reliable. Wouldn't hand it the riskiest changes unsupervised yet.
- Good defaults
- Responsive to feedback
- Setup docs assume more context than we had
Useful but needs guardrails
Works well for the narrow case we use it for. We had to add explicit boundaries after it did something a bit too enthusiastic in week one.
- Capable when scoped well
- Needs explicit boundaries
- Support response was slow
Genuinely changed how our team ships
We put this in front of real work for three weeks before trusting it near main. It's now part of the default flow, and reviewers spend their time on the parts that actually need judgment.
- Fast to set up
- Caught real bugs
- Occasional context loss on very large diffs
Would recommend with caveats
Good value for the price, and the team behind it ships improvements fast. Just don't expect it to read your mind about internal conventions on day one.
- Frequent updates
- Fair pricing
- Some rough edges in edge cases