DEVOPS
Scan code for stale feature flags and open removal PRs
Weekly scans your GitHub repository for feature flags that have been fully rolled out or untouched past a threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionSearch repo for flag references and datesGitHub
- LogicKeep flags past staleness threshold and fully rolled out
- ActionGenerate minimal removal diff per flagOpenAI
- ActionOpen one removal PR per stale flagGitHub
- OutputPost opened PRs to SlackSlack
What it does
Finds feature flags that have outlived their purpose and proposes their removal as code. Every week it walks the repo, cross-references each flag against its rollout state, and for any flag that is 100% on (or 100% off and long-dead) it opens a focused pull request that deletes the flag check and collapses the surviving branch.
When to use it
When flag debt is piling up and nobody has time to chase down which flags are safe to delete. Ideal for teams that gate features behind boolean flags and want a steady, low-effort cleanup cadence instead of a once-a-year purge.
How it works
- 1A weekly schedule kicks off the run.
- 2The repo is searched (GitHub code search) for all flag references and their last-modified dates.
- 3A logic step keeps only flags older than the staleness threshold whose rollout is fully resolved.
- 4For each surviving flag, an OpenAI step generates the minimal diff that removes the gate and keeps the live branch.
- 5A GitHub action opens one removal PR per flag, labeled `flag-cleanup`.
- 6A Slack message posts the list of opened PRs to the platform channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 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.