DEVOPS
Agentic Stale-Flag Triage and Owner Routing
An agent reviews each long-rolled-out flag, reads its code references and recent commit history, drafts a removal plan.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers triage
- ActionRetrieve flags past staleness thresholdHTTP webhook
- ActionSearch GitHub for flag references and authorsGitHub
- LogicAgent drafts removal plan and picks owner
- ActionCreate ClickUp task with plan and assigneeClickUp
- OutputPost triage digest to SlackSlack
What it does
This runs an agent over your stale-flag backlog. For each flag fully rolled out past the threshold, the agent inspects where the flag is referenced in the repo, summarizes what removing it entails, identifies the most likely owner from commit history, and creates a ClickUp task containing a concrete removal plan.
When to use it
Use it when raw "this flag is old" alerts aren't actionable enough and engineers ignore them. The agent does the upfront investigation — scope, blast radius, and owner — so each cleanup task arrives ready to start.
How it works
- 1A weekly schedule triggers the triage run.
- 2An action retrieves flags past the staleness threshold.
- 3For each flag, an action searches GitHub for code references and recent authors.
- 4The agent reasons over the references to draft a removal plan and pick an owner.
- 5An action creates a ClickUp task with the plan and suggested assignee.
- 6The output posts the triage digest to Slack for visibility.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.