ENGINEERING
Block PR merges during an active error-budget burn
When a pull request is marked ready, it checks the live Honeycomb burn rate for the service the PR touches and posts a blocking status check that fails if the SLO is burning too…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened or ready for reviewGitHub
- LogicMap changed paths to owning service + SLO
- ActionFetch live burn rate for that SLO from HoneycombHoneycomb
- LogicDecide pass/fail vs fast-burn threshold
- ActionWrite slo-burn-gate status check on the PRGitHub
- OutputComment gate result + SLO link on the PRGitHub
What it does
This enforces the burn-rate gate at the exact moment it matters — on the pull request itself. Instead of a repo-wide freeze, it evaluates reliability per PR and writes a pass/fail status check, so a single noisy service can block its own merges without halting unrelated work.
When to use it
Use it when you want per-service granularity and inline developer feedback rather than a blanket lock. Ideal for monorepos where one service's budget burn shouldn't stop the whole team.
How it works
- 1A GitHub trigger fires when a PR is opened or marked ready for review.
- 2A logic step maps the changed paths to the owning service and its Honeycomb SLO.
- 3An action pulls the current burn rate and remaining error budget for that SLO from Honeycomb.
- 4A logic branch decides pass or fail against the configured fast-burn threshold.
- 5An action writes a `slo-burn-gate` commit status check on the PR — green when healthy, red when burning.
- 6The output adds a PR comment explaining the gate result and linking the SLO.
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
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.