DEVOPS
Scan repo for flag references with no matching flag record
Greps the GitLab repo for flag-check call sites, compares them to the live flag registry in Postgres, and reports orphaned references and registry entries with zero code usage.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionClone repo and grep flag call sitesShell
- ActionFetch registered flag keysPostgres
- LogicDiff code vs registry into buckets
- ActionOpen GitLab triage issueGitLab
- OutputSummarize counts in SlackSlack
What it does
Reconciles your code against your flag registry. It scans the repository for every feature-flag evaluation call site, compares the set of keys found in code to the keys in your Postgres flag table, and flags two failure modes: code referencing flags that no longer exist, and registry flags that nothing in code reads.
When to use it
Use it when you suspect drift between what your flag service knows about and what the code actually checks. Orphaned references throw at runtime; unread registry flags are pure debt. This finds both before they bite.
How it works
- 1A weekly schedule starts the reconciliation.
- 2A shell step clones the repo and greps for the flag-evaluation pattern, emitting the set of referenced flag keys with file and line.
- 3A Postgres query returns the full set of registered flag keys.
- 4A logic step diffs the two sets into orphaned-in-code and unread-in-registry buckets.
- 5A GitLab action opens a tracking issue listing both buckets for triage.
- 6A Slack post summarizes counts and links the issue.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.