DEVOPS
On-Demand Removal Kit for a Single Feature Flag
Triggered by a webhook with a flag key, it verifies the flag is safe to remove via telemetry, gathers every call site.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook fires with target flag keyHTTP webhook
- LogicConfirm via Axiom flag is settled, else abortAxiom
- ActionGrep GitHub for all call sites of the flagGitHub
- ActionOpen GitHub removal PR with call-site manifestGitHub
- OutputCreate linked Linear tracking issueLinear
What it does
Gives an engineer a one-call way to retire a specific flag. You fire a webhook with the flag key; it confirms the flag is genuinely settled in telemetry, collects all references, and produces both a removal PR and a linked tracking issue so the cleanup is done and traceable in one shot.
When to use it
When you already know a flag should go — during a feature's final cleanup, a code review, or an incident retro — and want the call-site hunt and PR scaffolding done for you instead of grepping by hand.
How it works
- 1An HTTP webhook fires with the target flag key.
- 2Query Axiom to confirm the flag is fully rolled out or fully dormant; abort with a warning if it's still mixed.
- 3Grep GitHub for every call site of the flag key.
- 4Generate the removal diff inlining the surviving branch.
- 5Open a GitHub PR with the diff and call-site manifest.
- 6Create a linked Linear issue referencing the PR for tracking.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AxiomLog streams, queries, dashboards.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
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-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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.