DEVOPS
Agentic flag-debt triage that drafts a per-flag removal plan
An agent reviews each 90-day-stale flag, reads its call sites in the repo, judges removal risk, and posts a Confluence removal plan plus a Linear issue routed to the right owner.
How it runs
The automated pipeline, trigger to output.
- TriggerMonthly schedule
- ActionLoad stale flags with referencesPostgres
- ActionAgent reads flag call sitesGitLab
- LogicAssess removal risk and draft plan
- ActionPublish removal plan to ConfluenceConfluence
- ActionCreate owner-assigned Linear issueLinear
- OutputPost risk-ranked digest to SlackSlack
What it does
Runs an agent over your stale-flag list. For each flag fully rolled out 90+ days, the agent pulls the flag's code references, reasons about removal risk (shared helpers, nested flags, public API exposure), drafts a concrete step-by-step removal plan, and publishes it to Confluence with a linked Linear issue assigned to the owner.
When to use it
Use it when stale flags are non-trivial to remove and a blunt auto-MR would be risky. The agent does the judgment a senior engineer would do at triage, producing a plan a human can execute or approve.
How it works
- 1A schedule kicks off the monthly triage.
- 2A Postgres query loads stale flags with owners and reference paths.
- 3For each flag, the agent reads the relevant GitLab files to understand the call sites.
- 4The agent assesses risk and drafts a removal plan with ordered steps and rollback notes.
- 5A Confluence action publishes the plan page.
- 6A Linear issue is created per flag, linking the plan and assigned to the owner.
- 7A Slack digest lists every plan with risk level and links.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, 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.