ENGINEERING
Slow-Query Budget Gate on Pull Requests
On every PR that touches ORM query code, derive a p95 latency envelope from Honeycomb for the affected query patterns and fail the check if a new or changed query is projected…
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or updatedGitHub
- LogicExtract changed ORM query patterns from diff
- ActionFetch p95 latency for query shapesHoneycomb
- LogicCompare p95 vs per-endpoint budget
- OutputPost pass/fail commit status checkGitHub
What it does
This workflow turns Honeycomb's real production latency data into an enforceable budget that gates pull requests. When a PR changes ORM query code, it pulls the historical p95 latency for the matching query shapes, compares it against a per-endpoint budget, and posts a pass or fail GitHub check so slow queries never merge silently.
When to use it
Run it on any service where database latency is a recurring source of incidents and you want a hard line in CI rather than a post-deploy surprise. Best for teams already emitting query spans to Honeycomb.
How it works
- 1A pull request opened or synchronized event fires from GitHub.
- 2A logic step inspects the diff and extracts the ORM query patterns that were added or modified.
- 3A Honeycomb query fetches the p95 duration for each matching query shape over the trailing 7 days.
- 4A logic step compares each observed p95 against its configured budget and computes a pass or fail verdict with the worst offenders.
- 5A GitHub action posts a commit status check, blocking merge when any query is over budget.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect HoneycombDistributed traces and queries.
- 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.