ENGINEERING
Generate release notes from merged commits on tag
When you push a release tag, it gathers every merged commit since the previous tag, has an AI write clean, grouped release notes.
How it runs
The automated pipeline, trigger to output.
- TriggerRelease tag pushed (v*)GitHub
- ActionDiff commits since previous tagGitHub
- ActionDraft grouped release notes with AIOpenAI
- ActionPublish notes to GitHub ReleaseGitHub
- OutputAnnounce highlights in SlackSlack
What it does
On a new version tag, the workflow collects all commits merged since the last tag, summarizes them into human-readable release notes grouped by type (features, fixes, breaking changes), and publishes the result. It turns raw commit messages into notes a customer or teammate can actually read.
When to use it
When you cut releases by pushing semver tags and want consistent, well-organized release notes every time without writing them by hand. Ideal for teams using Conventional Commits or any reasonably structured commit history.
How it works
- 1A push of a tag matching your release pattern (such as v*) triggers the run.
- 2The workflow finds the previous tag and pulls the commit range between them from GitHub.
- 3An AI model reads the commit messages and PR titles and drafts notes grouped into Added, Fixed, Changed, and Breaking sections.
- 4It writes the generated notes to the GitHub Release body for that tag.
- 5It posts a short announcement with the highlights and a link to a release Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.