DEVOPS
File Linear Cleanup Tasks for Long-Dormant Feature Flags
Monthly, identifies flags that have not been evaluated at all (or only ever returned false) for 60+ days and files a Linear issue per flag with owner, age, and call sites…
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule fires
- ActionQuery Axiom for last-evaluated timestamp per flagAxiom
- LogicKeep flags dormant 60+ days or only-ever-false
- ActionResolve call sites and owning team via GitHub CODEOWNERSGitHub
- LogicLabel safe-delete vs needs-review by call-site presence
- OutputCreate a Linear cleanup issue per flag for the owning teamLinear
What it does
Surfaces zombie flags — keys that telemetry shows haven't been hit in two months, or have only ever returned false — and turns each into a Linear cleanup issue assigned to the owning team, complete with last-seen date and call-site references.
When to use it
For dormant or abandoned flags that never finished rollout. Unlike a fully-rolled-out cleanup, these need a human to decide whether to remove the flag and its dead-on-arrival branch, so this opens a tracked task rather than an automatic PR.
How it works
- 1A monthly schedule starts the sweep.
- 2Query Axiom for the last-evaluated timestamp and value distribution of every known flag key.
- 3Keep flags with zero evaluations in 60 days, or that returned only false historically.
- 4Look up call sites and the owning team via GitHub CODEOWNERS for each flag.
- 5Branch: flags with no call sites get a 'safe delete' label; flags still referenced get a 'needs review' label.
- 6Create one Linear issue per flag in the owning team's backlog with age, last-seen, and references.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 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.