DEVOPS
Open Removal PRs for Fully Rolled-Out Feature Flags
Weekly, scans Axiom telemetry for flags that have served 100% true for a sustained window, finds their call sites in the repo.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery Axiom for 30-day flag evaluation ratesAxiom
- ActionGrep GitHub repo for each flag's call sitesGitHub
- LogicDrop flags younger than 14 days or in active experiments
- ActionGenerate flag-removal diff inlining the enabled branch
- OutputOpen a GitHub removal PR per flag with call-site listGitHub
What it does
Finds feature flags that are effectively permanent — they've evaluated to the same value (typically 100% enabled) across every environment for weeks — and opens a code-level cleanup PR that deletes the flag check and inlines the winning branch, with the full call-site list in the description.
When to use it
When rolled-out flags pile up as dead conditionals and nobody circles back to remove them. Run it on a weekly cadence so cleanup stays continuous instead of becoming an annual debt sprint.
How it works
- 1A weekly schedule kicks off the run.
- 2Query Axiom for flag-evaluation events over the trailing 30 days and keep flags that served one value 100% of the time in all environments.
- 3For each candidate, grep the GitHub repo to collect every call site referencing the flag key.
- 4Skip flags added in the last 14 days or with active variant experiments.
- 5Generate the diff that removes the conditional and keeps the enabled path.
- 6Open a GitHub PR per flag with the call-site list and telemetry summary, ready for review.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.