DEVOPS
Open cleanup PRs for flags stuck at 100% for 30 days
Each week, finds feature flags that have served 100% rollout for 30+ days with no variation, then opens a GitHub PR that strips the flag and pins the winning branch.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the reaper run
- ActionPull flag evaluation metrics from DatadogDatadog
- LogicKeep flags at 100% with no change for 30+ days
- ActionFind flag code references in GitHubGitHub
- ActionOpen draft cleanup PR removing the flagGitHub
- OutputPost opened PRs to Slack for triageSlack
What it does
This workflow hunts down feature flags that have been fully rolled out (100% on one variation) for at least 30 days and have stopped changing. For each one it opens a draft GitHub pull request that deletes the flag and hardwires the live code path, so the cleanup is a review-and-merge instead of an investigation.
When to use it
Run it when your flag system has become a graveyard — dozens of flags that shipped months ago but were never removed, each one adding a dead branch and a config lookup. It is ideal for teams that treat flags as temporary release tooling rather than permanent config.
How it works
A weekly schedule fires the run. The workflow pulls flag evaluation metrics from Datadog and computes, per flag, the percent served and days since the last variation change. A filter keeps only flags at 100% for 30+ days. For each survivor it looks up the flag's code references on GitHub, opens a draft PR that removes the flag guard and keeps the winning path, and posts the list of opened PRs to Slack for the on-call engineer to triage.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.