ENGINEERING
Open a blame-tagged GitHub issue when a release regresses
When Sentry reports a regression on a new release, opens a GitHub issue pre-filled with the offending version, top error groups.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release regression alert webhookSentry
- ActionFetch top error groups and event countsSentry
- ActionPull commit range since last healthy releaseGitHub
- LogicMap changed paths to CODEOWNERS for likely owners
- ActionOpen a blame-tagged GitHub issueGitHub
- OutputLink the issue in the team Slack channelSlack
What it does
Turns a Sentry release regression into an actionable, owner-tagged GitHub issue so the fix starts immediately instead of in a triage meeting. It packages the version, the worst error groups, and the suspect commit range into one ticket.
When to use it
Use it when crash-free dips need engineering follow-up, not just a rollback. Best for teams that want a durable record and clear ownership for every release that misses its health bar.
How it works
- 1A Sentry regression alert webhook fires for a release that fell below its crash-free threshold.
- 2The flow fetches the release's top unresolved error groups and event counts from Sentry.
- 3It pulls the commit range from GitHub between this release and the last release that stayed healthy.
- 4A branch maps changed paths to CODEOWNERS to identify likely owners.
- 5It opens a GitHub issue with the version, error summary, commit list, and owner mentions, labeled as a release-health regression.
- 6A short Slack note links the new issue to the team channel.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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
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.