SUMMARIZATION
Sentry Regression to GitHub Issue with Commit Blame
When a deploy regresses Sentry error rates, correlates the spiking issues to the commits in that release's diff and files a GitHub issue with a regression brief and the likely…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel deploy succeededVercel
- ActionFetch Sentry deltas + top spiking issuesSentry
- LogicContinue only on regression
- ActionPull GitHub commit range between releasesGitHub
- ActionSummarize brief + map issues to culprit commitsOpenAI
- OutputOpen GitHub issue with regression briefGitHub
What it does
Closes the loop from regression to code owner. After a deploy, it measures the Sentry error-rate delta versus the prior release, and if errors worsened it pulls the GitHub commit range between the two releases, matches the spiking Sentry issues to the files they touch, and opens a GitHub issue. The issue contains a plain-English regression brief plus the commits most likely responsible and who authored them.
When to use it
Use it when regressions need an owner and a paper trail in your tracker, not just a Slack ping. It saves engineers the manual hunt of mapping an error spike back to which commit in the release introduced it.
How it works
- 1A Vercel deploy-succeeded webhook provides the new release SHA.
- 2Fetch Sentry error deltas and the top spiking issues versus the prior release.
- 3Branch: proceed only if a regression is present.
- 4Pull the GitHub commit range between the two release SHAs and map spiking issues to changed files.
- 5Summarize into a regression brief naming the suspect commits and authors.
- 6Open a GitHub issue with the brief and culprit commits.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect SentryErrors, performance, releases.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect OpenAIModels, embeddings, files.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.