Write release notes your customers will actually read

Zero reads the commits and merged PRs in your release, clusters the changes by customer impact, and drafts customer-facing release notes that are clear, specific, and ready to ship.

Zero connects:

Why release notes get written in a rush or skipped entirely

Release notes are always the last thing to get written and the first thing to get cut when the release is running late. The problem is the source material: commit messages written for engineers, PR titles that assume tribal knowledge, and 30 merged PRs that your users mostly don't care about individually. Release Notes Generator flips the workflow. Zero reads the commits and PR descriptions, filters for customer-visible changes, groups them by theme (new features, improvements, fixes), and writes the notes in the voice your customers actually read. You review, and the next release ships with notes instead of silence.

How to ask Zero to draft release notes

@Zero for the release we're shipping today, read all merged PRs since the last release tag. Group by customer impact: new features, improvements, bug fixes. Skip internal refactors and test changes. Draft customer-facing notes in our product voice.

try it

How Zero turns commits into customer-facing notes

Zero reads every merged PR in the release window

Zero pulls merged PRs since the last release tag, including titles, descriptions, and labels. Internal-only changes (refactors, tests, CI tweaks) get filtered out based on your label convention.

Zero groups changes by customer impact

Zero clusters the remaining PRs into themes: new features, improvements, and fixes. Each change gets rewritten from the PR description into a customer-facing line: specific enough to be useful, free of internal jargon.

Zero drafts the notes in your product voice

The final draft lands in your docs tool or Slack with sections that follow your release-notes template. You edit for voice and nuance, then publish.

Refine the voice, chain with publishing, translate

Refine the voice

Update the guidance Zero uses for tone and formatting.

@Zero from now on, skip Markdown headers in release notes. Plain prose only.

try it

Chain with publishing

Push the approved notes directly to your docs or blog.

@Zero once I approve the notes, publish them to the Releases section of our docs and post the link in #announcements.

try it

Translate

Generate notes in every locale you support.

@Zero translate the approved release notes into German, Japanese, and Spanish. Preserve the section structure.

try it

Required integrations: GitHub and Slack

GitHub

GitHub. Zero reads merged PRs, commit messages, labels, and release tags. Read access to the repo required.

Required

Slack

Slack. Zero delivers drafts to the review channel and posts the final notes once approved. Channel write access required.

Required

Best practices for automated release notes

●Tag internal-only PRs with a consistent label (like `internal` or `no-release-notes`). Zero can only skip what you mark.

●Keep a short style guide for release notes in your docs. Customer voice, active verbs, no internal jargon. Zero picks it up and applies it every release.

●Draft notes before the release ships, not after. Reviewing a draft while the work is fresh is faster than reconstructing context a week later.