DEVOPS
Agent-Driven Codebase Feature-Flag Audit and Cleanup
An agent crawls the repository on demand, reconciles in-code flag references against the flag registry.
How it runs
The automated pipeline, trigger to output.
- TriggerOperator starts audit manually
- ActionSearch all flag references in GitHubGitHub
- LogicReconcile against registry, classify flagsPostgres
- ActionOpen removal PR per stale flagGitHub
- ActionPublish audit findings to ConfluenceConfluence
- OutputPost audit digest to SlackSlack
What it does
Runs a full reconciliation between the flags your code references and the flags your registry knows about. An agent reads the codebase, finds orphaned references and expired flags, decides which are genuinely safe to remove, and opens a removal PR for each with a plain-English justification.
When to use it
Use it for a periodic deep audit rather than a quick scan, especially before a major release or when the flag registry has drifted out of sync with the code.
How it works
- 1An operator triggers the audit manually.
- 2The agent searches GitHub for every flag reference across the repository.
- 3It cross-checks each reference against the registry stored in Postgres, classifying flags as active, expired, or orphaned.
- 4For expired and orphaned flags it removes the code paths and opens a PR per flag with a rationale and risk note.
- 5A Confluence page is updated with the full audit findings as a durable record.
- 6A Slack digest links the new PRs and the audit page.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 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
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.