ENGINEERING
Tag New Flags with an Expiry Date When Their MR Opens
When a GitLab MR that introduces a new feature flag is opened, this records the flag with a default expiry date in Postgres and comments on the MR with the cleanup deadline.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened webhook firesGitLab
- LogicParse diff for newly added flag keys
- LogicExit if no new flag keys introduced
- ActionUpsert Postgres registry row with 90-day expiry and ownerPostgres
- OutputComment expiry deadline on the GitLab MRGitLab
What it does
Intercepts flag creation at the source. When a newly opened GitLab MR adds a feature-flag key that is not yet in the registry, it inserts a row in Postgres with a default expiry (creation date plus 90 days) and posts an MR comment stating the cleanup deadline and owner. Debt prevention rather than debt cleanup.
When to use it
Use this as the upstream complement to the other reapers: the best stale flag is one that never goes stale because it had an expiry from day one. Adopt it when starting a flag-hygiene program so new flags stop adding to the pile while older workflows drain the existing backlog.
How it works
- 1A GitLab MR-opened webhook fires.
- 2Parse the diff for newly added flag-key references.
- 3Branch: exit if the MR introduces no new flag keys.
- 4For each new key, upsert a Postgres registry row with a 90-day expiry and the MR author as owner.
- 5Post a GitLab comment on the MR naming the flag, its expiry date, and cleanup expectations.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.