DEVOPS
ChatOps On-Demand Feature-Flag Removal
Lets an engineer request removal of a named flag from Slack; the agent verifies it is past sunset and carries no live traffic, then opens a removal PR or explains why it refused.
How it runs
The automated pipeline, trigger to output.
- TriggerEngineer requests removal in SlackSlack
- ActionLook up flag in Postgres registryPostgres
- ActionCheck live traffic in DatadogDatadog
- LogicProceed only if past sunset and cold
- ActionOpen scoped removal PR in GitHubGitHub
- OutputReply in Slack with PR link or reasonSlack
What it does
Turns flag removal into a one-line Slack command. An engineer names a flag, and the agent independently verifies the flag is safe to remove before opening a PR. If it isn't safe, the agent says so and explains why, so removals stay deliberate.
When to use it
Use it when engineers want to retire a specific flag the moment they remember it, without waiting for the nightly sweep or hand-writing the PR.
How it works
- 1An engineer triggers the workflow from Slack with the flag name.
- 2The agent looks up the flag in the Postgres registry to confirm it exists and read its sunset date.
- 3It checks recent evaluation metrics in Datadog to confirm the flag carries no live traffic.
- 4A logic gate proceeds only if the flag is both past sunset and cold; otherwise it stops with a reason.
- 5On approval the agent opens a GitHub removal PR scoped to that flag.
- 6A Slack reply returns either the PR link or the explanation for the refusal.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect DatadogMetrics, traces, log search.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 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.