ENGINEERING
Weekly Stale Feature-Flag Scan with Auto-Cleanup MRs
Every Monday, scans your flag registry for flags that have been 100% rolled out for over 30 days.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule fires
- ActionQuery Postgres for 100%-rollout flags idle 30+ daysPostgres
- LogicDrop flags tagged permanent or kill-switch
- ActionSearch GitLab repo for each flag key and build removal diffGitLab
- ActionOpen one cleanup MR per stale flagGitLab
- OutputPost digest of opened MRs to SlackSlack
What it does
Finds feature flags that are fully rolled out (100% enabled) and have not changed state in over 30 days, then automatically opens one GitLab merge request per stale flag. Each MR removes the flag check and the now-dead `else` branch, leaving only the shipped code path.
When to use it
Run this when your codebase has accumulated dozens of permanent-by-accident flags. Teams that gate every feature behind a flag but never circle back to clean them up end up with brittle, hard-to-read conditionals. This turns a quarterly chore into a weekly trickle of small, reviewable MRs.
How it works
- 1A weekly schedule fires Monday morning.
- 2Query Postgres flag-state table for flags at 100% rollout with `last_changed_at` older than 30 days.
- 3Filter out flags tagged `permanent` or `kill-switch` so operational toggles survive.
- 4For each remaining flag, search the GitLab repo for its key and generate a diff that deletes the branch.
- 5Open a GitLab MR per flag with the diff, a checklist, and reviewers auto-assigned.
- 6Post a digest to Slack listing the MRs opened so the team can triage.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
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.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.