ENGINEERING
Stale Feature-Flag Cleanup PR After 100% Rollout
Watches your flag-management Postgres table for flags that have sat at 100% rollout past a grace window.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionQuery Postgres for flags past grace window at 100%Postgres
- ActionSearch repo for all references to each flag keyGitHub
- ActionRewrite files to remove flag and keep live pathOpenAI
- ActionOpen draft cleanup PR per flagGitHub
- OutputPost PR links to engineering SlackSlack
What it does
Finds feature flags that finished rolling out and have been fully enabled long enough to be considered permanent, then drafts the cleanup PR a human would otherwise write by hand. The outcome is a ready-to-review branch that removes the flag check and collapses the kept code path.
When to use it
Run it nightly when your team ships behind flags and tends to leave them in the code months after the rollout is done. Best for codebases where flag checks follow a consistent pattern an LLM can rewrite reliably.
How it works
- 1A nightly schedule fires the workflow.
- 2Query Postgres for flags at 100% rollout whose `fully_enabled_at` is older than the grace window (e.g. 30 days).
- 3For each candidate, search the GitHub repo for every reference to the flag key.
- 4Send the matched code spans to OpenAI to rewrite each file with the flag removed and the live branch kept.
- 5Open a draft PR per flag with the rewritten files and a checklist of touched call sites.
- 6Post the PR link to the engineering Slack channel for an owner to claim.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect OpenAIModels, embeddings, files.
- 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 Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.