ENGINEERING
Detect Orphaned Flags When a Flag-Removal MR Merges
Listens for merged GitLab MRs, and when one removes a feature flag from code, checks whether the flag still exists in the runtime registry.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR merged to default branchGitLab
- LogicParse diff for deleted flag-key references
- LogicExit if no flag keys were removed
- ActionQuery Postgres for still-active flag definitionsPostgres
- OutputPost Slack orphan-flag archive reminderSlack
What it does
Reacts to merged GitLab merge requests. When a merge deletes references to a flag key from the codebase but the flag still exists as an active definition in the registry, it flags the mismatch: the code is gone but the config lingers, leaving an orphan that can confuse the next engineer.
When to use it
Use this when your flag cleanup involves two systems that drift apart: the code (in GitLab) and the live flag definitions (in Postgres or your flag service). Removing the conditional in code does not automatically retire the flag record. This catches that exact gap right at merge time, when context is freshest.
How it works
- 1A GitLab merge webhook fires when an MR lands on the default branch.
- 2Parse the diff to extract any flag keys whose references were deleted.
- 3Branch: if no flag keys were removed, exit quietly.
- 4For each removed key, query Postgres to check whether the flag is still defined and active.
- 5If the flag still exists, post a Slack message tagging the merger with a one-click link to archive it.
- 6Log the orphan resolution outcome for audit.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.