ENGINEERING
EXPLAIN ANALYZE Evidence Comment for Risky Queries
When a PR adds a query flagged as over its latency envelope, run EXPLAIN ANALYZE against a Postgres replica and post the plan plus the Honeycomb baseline as a PR comment…
How it runs
The automated pipeline, trigger to output.
- TriggerPR review requestedGitHub
- LogicIdentify flagged query and bind sample params
- ActionRun EXPLAIN ANALYZE on replicaPostgres
- ActionFetch Honeycomb p95 baselineHoneycomb
- OutputPost execution plan PR commentGitHub
What it does
When a pull request introduces a query that the budget gate flags as risky, this workflow gathers concrete evidence instead of just a red X. It runs EXPLAIN ANALYZE on a read replica and posts the execution plan alongside the Honeycomb p95 baseline as an inline PR comment, giving reviewers the data to approve or reject quickly.
When to use it
Use it to make slow-query reviews fact-based. Ideal when reviewers lack database expertise and need the planner output and production baseline served to them in the PR.
How it works
- 1A pull request review-requested event fires from GitHub.
- 2A logic step identifies the flagged query and substitutes representative bound parameters.
- 3A Postgres action runs EXPLAIN ANALYZE against a non-production replica and captures the plan, cost, and row estimates.
- 4A Honeycomb action fetches the current p95 baseline for the same query shape for comparison.
- 5A GitHub action posts a formatted PR comment with the plan, the baseline, and a flag on sequential scans or bad estimates.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect HoneycombDistributed traces and queries.
- 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.