ENGINEERING
Budget-Recovery Freeze Lift and Deploy Gate
On each pull request, this workflow checks whether the service's Datadog error budget has recovered above the safe threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updatedGitHub
- ActionRead remaining budget and burnDatadog
- LogicCompare to recovery threshold
- ActionSet commit status pass or blockGitHub
- OutputNotify PR author in SlackSlack
What it does
This closes the loop after a feature freeze. Rather than a human deciding when shipping is safe again, it gates pull requests on live budget health: it reads the current remaining error budget from Datadog and reports a GitHub commit status that either lifts the freeze (budget recovered) or holds it (still below threshold).
When to use it
Use it once a freeze has been declared and you want merges blocked until the budget genuinely recovers, with the decision driven by data and enforced in the PR itself. It complements the freeze-trigger workflow that opens the freeze in the first place.
How it works
- 1A GitHub pull-request event triggers the check.
- 2It reads the service's remaining error budget and recent burn rate from Datadog.
- 3A logic step compares remaining budget against the recovery threshold and decides pass or block.
- 4It posts a GitHub commit status: success with a "freeze lifted" note when recovered, or failure with current budget and the threshold when not.
- 5It notifies the PR author in Slack so they know why the gate passed or held.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DatadogMetrics, traces, log search.
- 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
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.