ENGINEERING
Guard merged PRs against latency regressions with a Honeycomb check
After a pull request merges and deploys, compares post-deploy span latency in Honeycomb to the pre-merge baseline and, if a regression is detected, comments on the PR and opens…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub pull_request merged event firesGitHub
- ActionAfter settle delay, query Honeycomb for post-deploy span latencyHoneycomb
- LogicCompare to pre-merge baseline; decide if regressed
- ActionComment latency delta and offending query on the PRGitHub
- OutputOpen follow-up GitHub issue linking PR and traceGitHub
What it does
When a PR merges and the deploy completes, it waits for traffic to flow, then compares the affected endpoint's latency in Honeycomb against the baseline captured before the merge. If latency regressed, it attributes the blame to the PR and reports back on the PR itself.
When to use it
When you want a lightweight performance gate that catches regressions slipping past CI — the kind that only show under real production load. Best for teams that deploy on merge and want accountability tied directly to the PR that shipped the change.
How it works
- 1A GitHub `pull_request` merged event fires the workflow.
- 2After a settle delay, query Honeycomb for the endpoint's post-deploy p99 and the slowest span breakdown.
- 3A logic step compares against the stored pre-merge baseline and decides if the regression exceeds the tolerance.
- 4If regressed, comment on the merged PR with the latency delta and the offending query.
- 5Open a GitHub issue linking the PR, the trace, and the suspect query for follow-up.
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
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.