Engineers tag a release and move on, leaving support and sales to guess what actually shipped. This bot turns the merge history into notes anyone can read.
sonnet3 daysGitHubOpenAILinearSlack
Claude
66ROI
89Scale
$1.4k93Saved
ROI for
README.md
Why this subagent
Engineers tag a release and move on, leaving support and sales to guess what actually shipped. This bot turns the merge history into notes anyone can read.
It collects the PRs since the last tag, groups them into features and fixes, drops the internal noise, and rewrites each change in plain language. The notes get published to your channel with the version and date, so the whole company learns what changed without reading a single commit message.
How it runs
Used at step 01 to kick off the pipeline.
Write
Used at step 01 to kick off the pipeline.
WebFetch
Used at step 01 to kick off the pipeline.
WebSearch
Used at step 01 to kick off the pipeline.
Group changes into features, fixes, and internal work, dropping noise like dependency bumps.
pending
Rewrite each user-facing change in plain language a non-engineer can follow.
pending
Publish the notes to the chosen channel and attach the version and date.
pending
Sample output
json
// Sample output
// (generated when the pipeline finishes)
Given merged PRs since the last tag, return release notes grouped into features and fixes, each rewritten in plain language for a non-technical reader.
Unlock the rest
The full agent definition, install snippet, and starter task are gated for community members.
Members get the full `.md` agent file, the npm / pnpm install one-liners, a starter prompt that we've tuned against real runs, and the open-source repo when this automation ships there. One email, magic link, done.