Automated Release Notes with AI agents

An agent can compile release notes automatically by scanning every PR merged since the last release, cross-referencing the linked ticket for user-facing context, and drafting categorized notes — new features, fixes, breaking changes — ready for a product manager to review before publishing. This replaces the last-minute scramble where someone tries to remember what actually shipped by skimming a week of Slack messages, and it means release notes actually reflect what merged rather than what the person writing them happened to recall.

How it works today vs. with Neotask

Release notes are almost always written under time pressure, right before a release goes out, by someone reconstructing "what changed" from memory and a quick scroll through recent PRs. That reconstruction misses things — a bug fix that didn't get a ticket, a UI tweak nobody thought was release-note-worthy but a customer definitely will notice, a breaking API change buried in a PR titled "cleanup." The categorization step is its own manual slog: sorting a list of PRs into features versus fixes versus breaking changes, and writing user-facing language instead of the internal engineering description from the PR title, takes real editing time that gets rushed right before a ship. And because it's manual, it's inconsistent release to release — sometimes detailed, sometimes a two-line summary — which erodes customer trust in the changelog as a reliable source. An agent scans the full merged PR list against the release window every time, so nothing that shipped is missing from the notes, and drafts in consistent, user-facing language a PM only has to edit, not write from scratch.

The agent flow

Scan merged PRs since the last release

The agent pulls every PR merged into the release branch since the previous release tag, so nothing that shipped is missed.

Integration: github

Cross-reference linked tickets

For each PR, it pulls the linked ticket to understand the user-facing intent behind the change, not just the internal code description.

Integration: linear

Draft categorized notes

Changes are drafted into features, fixes, and breaking changes, in plain customer-facing language rather than engineering shorthand.

Route to the PM for review

The draft goes to the product manager for review and edits before anything is published, since tone and emphasis still benefit from a human pass.

Integration: slack

Publish to the changelog

Once approved, the final notes are published to the canonical changelog space.

Integration: notion

Announce the release

The agent posts the release announcement to the internal team channel and, where configured, the customer-facing channel, with a link to the full notes.

Variations

• Internal-only releases (infra changes, backend refactors) skip the customer-facing announcement step and publish only to the internal engineering changelog.
• Breaking changes get a dedicated migration-guide section drafted alongside the standard notes, flagged prominently at the top.
• Weekly release cadences batch several days of merged PRs into one digest instead of publishing notes per individual deploy.

Frequently asked questions

What if a PR has no linked ticket at all?

The agent still includes it in the draft, summarizing directly from the diff and PR description, and flags it as ticket-less so the PM knows to double check the framing.

Does it publish automatically without review?

No — every draft goes through a PM review step before publishing; the agent handles the compilation and drafting, not the final go-live decision.

How does it distinguish a breaking change from a regular fix?

It looks for explicit signals — a ticket or PR tagged as breaking, API version bumps, removed endpoints — and flags anything ambiguous for the PM to classify manually rather than guessing.

Plans

Continue