Pulls merged PRs, auto-drafts release notes with features/fixes/breaking changes. Cuts release communication time from hours to minutes. Human review gate included.
Release notes are the tax you pay for shipping. Most teams skip them, batch them, or write them from memory three weeks late. The Release Notes Agent watches your Git history and drafts structured notes before you even ask. How it works: Every merged PR triggers a webhook. The agent extracts title, description, labels, and diff context. It classifies each change (feature, fix, breaking, chore, security). It drafts a markdown file with sections, links back to PRs, and flags anything that needs human judgment. You review, edit, approve, and publish. No more hunting through Slack or Jira for "what shipped this week." The real win isn't speed—it's consistency. Every release gets the same structure. Every breaking change gets flagged. Every security fix gets labeled. Your changelog becomes queryable. Your customers stop asking "did this fix my issue?" because they can search it themselves. The agent works best when your team uses consistent PR naming (feat:, fix:, breaking:) and descriptions. If your PRs are "wip" and "stuff," the agent will draft garbage—but that's a team problem, not a tool problem. Some teams use this to enforce better PR hygiene. Others use it to retrofit structure onto existing repos. The approval gate is critical. You're not automating judgment; you're automating grunt work. The agent flags uncertain classifications, suggests copy, and waits for a human to sign off before publishing. This prevents the "we shipped a breaking change and nobody noticed" scenario. Integration points: GitHub, GitLab, Bitbucket (via webhook). Output formats: Markdown, HTML, JSON. Publish destinations: Notion, Slack, email, static site generators. Some teams wire it to their changelog tool (Changelog.com, Coda, Markdown files in Git). Others use it to pre-fill a Notion database that their marketing team edits and ships. Common failure modes: PRs with no description (agent guesses wrong). Inconsistent labels (agent can't classify). Merged commits that should have been squashed (agent treats them as separate changes). Monorepos where multiple services ship in one PR (agent needs custom parsing rules). None of these are blockers—they're tuning problems.
Privacy notes
Agent reads PR titles, descriptions, and code diffs from your Git provider. Sensitive data in PR descriptions (API keys, customer names, internal URLs) will be included in drafts—sanitize before publishing or configure the agent to redact patterns. Release notes are typically public; treat them as such. Some teams run the agent on a private instance to avoid sending code to third-party APIs.