ENGINEERING
Triage merged PRs into a customer-facing changelog draft
On each merge to main, an agent decides whether the change is customer-facing; if so, it drafts a plain-language changelog entry and appends it to a pending-release doc…
How it runs
The automated pipeline, trigger to output.
- TriggerPR merged to mainGitHub
- LogicAgent classifies customer-facing vs internal
- ActionDraft plain-language changelog entry
- OutputAppend entry to pending-release docConfluence
What it does
Whenever a PR merges to main, an agent reads the PR title, description, and labels to judge whether the change is something a customer would notice (a new feature, a visible fix, a behavior change) versus internal-only work like refactors or test changes. For customer-facing changes it rewrites the technical summary into a clear, benefit-oriented changelog line and appends it to a running pending-release document for a human to approve before the next release.
When to use it
When you maintain a public changelog and the hard part is continuously deciding what is worth telling customers and phrasing it in their language. Best for teams that merge frequently and want the draft built up incrementally rather than scrambled together at release time.
How it works
- 1A GitHub webhook fires when a PR is merged into main.
- 2An agent classifies the change as customer-facing or internal using the PR content and labels.
- 3A logic branch drops internal-only changes and stops.
- 4For customer-facing changes, the agent drafts a plain-language entry from the technical details.
- 5It appends the entry, tagged as unreleased, to the pending-release Confluence page for human review before publishing.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.