DEVOPS
Scan code for flags past kill-date and file Linear cleanup tickets
Weekly scans your GitHub repos for feature flags whose kill-date has passed, then opens a Linear ticket for each one with the file locations and owning team.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionSearch GitHub repos for flag refs and kill-datesGitHub
- LogicKeep flags past kill-date, dedupe by key
- ActionOpen a Linear issue per expired flag with code linksLinear
- OutputPost cleanup digest to SlackSlack
What it does
Finds feature flags that should already be gone. It reads kill-dates from flag annotations in your codebase (e.g. `// @kill-date: 2026-03-01`), compares them to today, and creates one Linear issue per expired flag — pre-filled with every file and line where the flag still appears.
When to use it
When flag debt piles up faster than anyone cleans it. Teams add flags for launches and forget them; this gives each stale flag an owner and a ticket instead of letting it rot in `if` branches forever.
How it works
- 1A weekly schedule fires the run.
- 2The flow searches your GitHub repos for flag references and parses the `@kill-date` annotation on each.
- 3A logic step keeps only flags whose kill-date is before today and dedupes by flag key.
- 4For each expired flag it gathers the file paths, line numbers, and the team listed in the annotation.
- 5It opens a Linear issue per flag, assigned to the owning team, with a removal checklist and code links.
- 6It posts a digest to Slack summarizing how many tickets were filed.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.