DEVOPS
Reconcile Statsig flags against code and flag orphans in Slack
Compares your Statsig feature-gate registry against actual flag references in your GitHub code.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled reconciliation run
- ActionFetch all feature gates from Statsig APIHTTP webhook
- ActionCollect flag references from GitHub reposGitHub
- LogicDiff into orphaned gates and dead code refs
- OutputPost categorized drift report to SlackSlack
What it does
Keeps Statsig and your codebase honest with each other. It pulls the full list of feature gates from the Statsig API and the full list of flag references from your repos, then computes two drift sets: gates with zero code references (orphans, safe to archive) and code references pointing at gates that no longer exist (dead checks).
When to use it
When nobody trusts the Statsig dashboard anymore because half the gates haven't been touched in a year. Run it before a cleanup sprint to get a precise, evidence-backed list instead of guessing.
How it works
- 1A scheduled run kicks off the reconciliation.
- 2An HTTP call fetches all feature gates and their last-checked timestamps from the Statsig console API.
- 3A GitHub search collects every flag key referenced across your repos.
- 4A logic step diffs the two sets into orphaned gates and dead code references.
- 5It posts a categorized report to Slack with archive candidates, dead checks, and last-evaluated dates so a human can approve removals.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.