ENGINEERING
Comment a burn-gate verdict on every PR while budget is burning
On each new or updated PR, checks the affected service's live Honeycomb burn rate and posts a comment that either clears the PR or warns that the service is in a burn freeze.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened or updatedGitHub
- ActionMap changed paths to owning service and SLO
- ActionQuery Honeycomb for current burn rate and budgetHoneycomb
- LogicDecide verdict: clear, caution, or freeze
- OutputPost or update burn-gate verdict comment on the PRGitHub
What it does
Adds a per-PR reliability check. Whenever a PR is opened or pushed, it looks up the current burn rate of the service that PR touches and leaves a comment: green if budget is healthy, a hold warning if the service is actively burning its error budget.
When to use it
Use it when you want the burn signal to meet engineers exactly where they work, on the PR, without a hard branch-protection block. It gives reviewers context to decide whether to merge now or wait.
How it works
- 1A GitHub pull_request event (opened or synchronized) triggers the flow.
- 2The flow maps the changed paths to an owning service and its Honeycomb SLO.
- 3It queries Honeycomb for that SLO's current burn rate and remaining budget.
- 4A logic step decides the verdict: clear, caution, or freeze based on configured thresholds.
- 5It posts (or updates) a single PR comment stating the verdict, the live burn numbers, and a link to the SLO dashboard.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HoneycombDistributed traces and queries.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.