ENGINEERING
Merge-request preflight EXPLAIN regression gate
On every merge request, runs EXPLAIN ANALYZE for the queries it touches against a production-like replica, compares estimated cost and rows to the base branch.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge-request open/update webhookGitLab
- ActionRun EXPLAIN ANALYZE on replica for both branchesPostgres
- LogicDiff cost/rows/scan type and apply regression threshold
- OutputComment pass/fail verdict on the merge requestGitLab
What it does
When a merge request opens or updates, this workflow detects the SQL it changes, runs EXPLAIN ANALYZE for each touched query against a production-like Postgres replica on both the MR branch and the base branch, and diffs planner cost, estimated rows, and scan types. If a query regresses to a sequential scan or its cost balloons past threshold, the workflow posts a blocking comment on the MR; otherwise it posts a green preflight note. The goal is to catch the regression before it ships, not after.
When to use it
Use this as a guardrail on repos where query performance regressions are expensive to roll back. It shifts slow-query detection left into code review so reviewers see a concrete plan diff next to the diff itself.
How it works
- 1GitLab merge-request webhook fires on open or update.
- 2Run EXPLAIN ANALYZE for touched queries on the replica for both branches.
- 3Diff cost, estimated rows, and scan type between branches.
- 4Branch on whether any query breaches the regression threshold.
- 5Comment a blocking fail or a green pass back on the merge request.
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
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.