ENGINEERING
EXPLAIN Plan Diff on Every Deploy
When a deploy completes, re-runs EXPLAIN on your tracked hot queries, diffs the new plans against the pre-deploy plans.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deploy-success webhookVercel
- ActionRun EXPLAIN on tracked queriesPostgres
- ActionLoad last-good plansPostgres
- LogicDetect scan downgrade or cost spike
- OutputAlert Slack with deploy SHASlack
- ActionStore new plan baselinePostgres
What it does
It catches query plan regressions caused by a deploy. On each Vercel deploy webhook it runs `EXPLAIN (FORMAT JSON)` for a curated list of hot queries against production Postgres, compares the new plan tree to the last-known-good plan, and detects dangerous changes — an index scan flipping to a seq scan, a nested loop becoming a hash join on a large relation, or estimated cost ballooning.
When to use it
Use this when migrations or ORM changes quietly invalidate the planner's choices. It ties plan changes directly to the deploy that caused them so you can revert with confidence.
How it works
- 1Vercel deploy-success webhook triggers the run.
- 2Run `EXPLAIN (FORMAT JSON)` for each tracked query against Postgres.
- 3Load the stored last-good plan for each query.
- 4A logic step compares node types and costs, flagging scan-type downgrades or cost spikes.
- 5Post a Slack alert with the deploy SHA and the offending plan nodes.
- 6Save the new plans as the next baseline.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 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
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.