DEVOPS
Weekly stale feature-flag sweep with cleanup PRs
Every week, scans the flag provider for flags that have been fully rolled out or untouched past a threshold, opens a GitHub PR removing the flag's dead code paths.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires the sweep
- ActionFetch all flags and rollout state from providerHTTP webhook
- LogicKeep only flags past the staleness threshold
- ActionOpen a draft cleanup PR per stale flagGitHub
- OutputDM the flag owner the PR link in SlackSlack
What it does
Runs a scheduled hygiene sweep over your feature flags. It finds flags that are stale — 100% rolled out for longer than your grace period, or with zero evaluations in the last N days — and for each one opens a draft GitHub pull request that strips the flag guard and keeps the winning code path. It then notifies the flag's owner in Slack so a human reviews and merges.
When to use it
Use it when flags pile up after launches and nobody circles back to delete them. Good for teams that treat flags as temporary release tooling and want a standing janitor instead of a quarterly manual audit.
How it works
- 1A weekly schedule fires the sweep.
- 2An HTTP call pulls the full flag list and rollout state from your flag provider.
- 3A logic step keeps only flags past the staleness threshold (fully rolled out or unevaluated).
- 4For each survivor, GitHub opens a draft cleanup PR removing the flag's branches.
- 5Slack DMs the owner the flag name and PR link for review.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 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.