DEVOPS
Stale Feature-Flag Sunset Scanner with Auto Removal PR
Runs nightly to find feature flags whose sunset date has passed, then opens a GitHub PR that deletes the flag's code branches and config entry so dead flags don't pile up.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionRead flag registry from PostgresPostgres
- LogicKeep flags past sunset date
- ActionOpen removal PR per stale flagGitHub
- OutputPost new PR list to SlackSlack
What it does
Scans your feature-flag registry every night, finds any flag whose sunset date is in the past, and opens a focused GitHub pull request that strips the flag from both code and config. Each stale flag becomes one reviewable PR instead of a backlog item nobody touches.
When to use it
Use it when your team adds flags faster than it removes them and 'temporary' flags have started living for months. Best for orgs that already record a sunset or expiry date alongside each flag.
How it works
- 1A nightly schedule fires the run.
- 2The flag registry table in Postgres is read and each flag's sunset date is compared to today.
- 3A logic step keeps only flags whose sunset date has already passed.
- 4For each stale flag, GitHub is searched for every reference, the conditional branches are collapsed to the shipped path, and the config entry is removed.
- 5A pull request is opened per flag with the diff, the original sunset date, and a removal checklist.
- 6A Slack message posts the list of new removal PRs to the platform channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 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.