DEVOPS
Escalate overdue flag-removal tickets into a weekly digest
Each week it finds Linear flag-removal tickets that are past their due date, builds a ranked owner-by-owner digest.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionFetch overdue flag-removal issuesLinear
- LogicGroup by owner and rank by overdue severity
- ActionWrite owner-by-owner digestOpenAI
- OutputPost digest to engineering channelSlack
- ActionFile low-urgency note for top offendersPagerDuty
What it does
Turns silent, ignored flag-debt tickets into visible accountability. It pulls every overdue flag-removal issue from Linear, groups them by owner, ranks owners by how overdue and how many tickets they hold, and publishes a digest that makes the backlog impossible to ignore.
When to use it
When flag-removal tickets get filed but never finished. Use this when you already track flag debt in Linear and need a recurring nudge that surfaces the worst offenders without a manager manually combing the board.
How it works
- 1A weekly schedule starts the run.
- 2A Linear query fetches open flag-removal issues past their due date.
- 3A logic step groups them by assignee and ranks by overdue days and ticket count.
- 4An OpenAI step writes a concise, owner-by-owner digest with the top offenders called out.
- 5The digest posts to the engineering channel in Slack.
- 6For any owner above the escalation threshold, a PagerDuty low-urgency note is filed.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.