Automated release notes from your merged PRs
GitLoom is a Slack-first pull request notification tool with a built-in release notes generator: it reads your merged pull requests and commits, writes plain-English release notes, and delivers them to Slack or email on schedule.
No changelog doc to keep alive, no digging through git log on release day. And if nothing shipped, GitLoom stays quiet.
Release notes: 4 changes shipped across 2 repos this week.
New: web#512 CSV export for invoice history (Priya)
Customers can now download their full invoice history as a CSV from Billing settings.
Improved: api#498 Faster search indexing (Jonas)
Search results now reflect changes within seconds instead of minutes.
Fixed: api#505 Webhook retries dropped on timeout (Ale)
Timed-out webhook deliveries are now retried correctly instead of being dropped.
Fixed: web#508 Invite screen showed placeholder text (Tom)
The invite screen no longer shows placeholder copy when a team has no pending invites.
The same notes went out by email. Copy, edit, or share them as-is.
Drafted from merged PRs. Nobody wrote this by hand.
Release notes are always someone’s chore
Every team means to keep a changelog. Then a deadline hits, the release ships, and the notes get postponed until things calm down. Three releases later, nobody remembers what actually changed.
The raw material is scattered too. The truth of a release lives across merged PRs, commit messages, and closed tickets. Turning "fix race condition in retry queue" into a sentence a customer understands takes real time, and it always lands on whoever drew the short straw.
So the work ships silently. Customers never hear about the fix they asked for, support fields questions the release notes should have answered, and stakeholders keep asking what the team did all month.
The git log is not customer-readable
Commit messages are written for reviewers, not readers. "refactor: extract webhook client" means nothing outside the repo.
Manual changelogs go stale
A changelog updated "when someone remembers" stops being trusted after the second missed release.
The writer was not in every PR
Reconstructing a release means re-reading diffs and pinging authors for context, usually on release day.
Silence looks like inactivity
If you never announce what shipped, customers and stakeholders quietly assume nothing did.
Release notes that write themselves
The Release Notes report turns merged work into notes people actually read. It is AI release notes in the practical sense: GitLoom reads what your team merged and explains it in plain English.
Generated from merged PRs and commits
GitLoom watches the GitHub repos you connect and drafts notes from what actually merged. No forms to fill, nothing extra to tag.
Plain English, not commit-speak
"fix: retry idempotency #505" becomes "Timed-out webhooks are now retried correctly." Readable by customers, support, and sales.
Delivered to Slack, email, or Telegram
Notes land where people already read. Post them to #releases for the team, send them to stakeholders by email, or both.
On schedule, without babysitting
Turn the report on once and it keeps firing. No release-day scramble, no "who is writing the notes this time?"
Quiet by default
If nothing merged since the last report, GitLoom stays silent. No empty "no updates this week" posts cluttering the channel.
A draft you can ship or polish
Use the notes as-is for internal channels, or copy and edit them before they go to customers. Either way, the blank page is gone.
Set up in about two minutes
No YAML, no release scripts, no changes to your CI. GitLoom reads each repo and detects your release convention (version tags, a deploy branch, or continuous merges to main), and you can override anything with pickers showing your real branches.
Install the GitHub App
Grant access to the repos you want covered. Repos you grant during install are tracked automatically.
Connect Slack or email
Pick where release notes should land: a Slack channel, email, or Telegram. Most teams start with #releases.
Turn on Release Notes
Enable the report, point it at your channel, and send yourself a test before going live. The next batch of merged work arrives already written up.
Frequently asked questions
Prefer to write your own from a starting point? A gallery of release notes templates is coming to our resources section.
Your next release notes, already written.
Turn on the Release Notes report and the next batch of merged work arrives in Slack, written up and ready to share.
Two minutes to install · 14 days free · Quiet by default