DEVOPS
Agentic Flag Cleanup: Investigate, Plan, and Open a Safe Removal MR
An agent takes a single stale flag, traces every usage across the GitLab repo, decides which branch is now permanent, and opens a reviewed removal MR with a written rationale.
How it runs
The automated pipeline, trigger to output.
- TriggerManual trigger with target flag key
- ActionSearch and read all flag usages in repoGitLab
- LogicAgent determines surviving branch
- ActionOpen removal MR with written rationaleGitLab
- OutputPost MR link and reasoning to SlackSlack
What it does
For one stale flag, an agent investigates all references in the codebase, reasons about which conditional branch is the surviving behavior, removes the dead branch and the flag definition, and opens a GitLab MR. It writes a plain-English rationale explaining what it kept and why, then posts the link to Slack.
When to use it
Use this for flags whose removal isn't a mechanical delete, where guards wrap meaningful logic and a human needs to trust that the right branch survived. The agent does the reading and reasoning that makes a mechanical harvester unsafe on its own.
How it works
- 1A manual trigger supplies the flag key to clean up.
- 2The agent searches the GitLab repo for every reference and reads the surrounding code.
- 3It reasons about the default/rollout state to determine the permanent branch, handling nested and negated guards.
- 4It produces a patch, opens an MR with a rationale and a reviewer assigned.
- 5It posts the MR link and its reasoning summary to Slack for sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.