Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes them on GitHub, and files a changelog entry in Notion.
The prompt
This is the whole configuration
Paste it into a workflow and edit it in plain English. There is nothing else to wire up.
When a tag is created, compare it against the previous tag and read every merged pull request between them, including the bodies and the linked issues. Group the changes into Features, Improvements, Fixes, and Breaking changes. Write each entry for a user of the product rather than a contributor to it — say what changed for them, and skip internal refactors entirely. For any breaking change, include a short migration snippet. Publish the draft release on GitHub with these notes, then create a matching entry in the Notion Changelog database with the same content and a link to the release.
Trigger
What starts this agent
Runs when the event fires in the connected service. Filter on the fields that matter so only the runs you want wake the agent.
Example output
What you get back
Every run leaves a readable record: the steps the agent took and the result it produced.
Draft release v2.8.0
- Features — 6 entries, led by scheduled exports
- Fixes — 11 entries, grouped by area
- Breaking — 1 entry, with a migration snippet
New to Helios? Start with Run your first agent.
Related templates
Pair it with these
Engineering
Pull request reviewer
Reviews every pull request against your conventions, leaves inline comments, and posts a weekly digest of review load and CI health.
Marketing
Discord community digest
Reads every channel each evening, surfaces unanswered questions, and files real bug reports as GitHub issues.
Support
Documentation freshness audit
Checks your written docs against the actual codebase every month and comments on the pages that have gone stale.
Run Release notes writer on your stack.
Connect the integrations, paste the prompt, attach the trigger. The agent takes it from there.