DEVOPS
Zero-Evaluation Dead Flag Detector
Inspects flag evaluation telemetry to find flags that no running code has checked in weeks, confirms they are absent from the repo.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule triggers sweep
- ActionPull per-flag evaluation countsPostgres
- LogicKeep flags with zero evaluations
- ActionSearch repo for flag referencesGitHub
- LogicSplit orphaned vs still-referenced
- OutputFile Linear deletion ticketLinear
What it does
Identifies feature flags that are defined in your flag store but have recorded zero evaluations across a long window, meaning no live code path references them anymore. It cross-checks the codebase to confirm the flag key truly has no call sites, then files a deletion ticket.
When to use it
Use it when flags accumulate faster than they get removed and you need evidence-based confirmation that a flag is genuinely dead before deleting its definition.
How it works
- 1A schedule triggers the sweep each month.
- 2It pulls per-flag evaluation counts from Postgres telemetry for the lookback window.
- 3A filter keeps only flags with zero evaluations in that window.
- 4For each candidate it searches GitHub for any remaining reference to the flag key.
- 5A branch splits flags into truly-orphaned (no code, no evals) versus suspicious (no evals but still referenced).
- 6For orphaned flags it opens a Linear deletion ticket; suspicious ones get flagged for manual review.
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 LinearIssues, projects, cycles, triage.
- 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.