SUMMARIZATION
Regression brief commented back on the merged PR
When a GitHub PR merges and its release deploys, watches Sentry for new error groups tied to that release, clusters them by root cause.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR merged webhookGitHub
- ActionFetch release-scoped Sentry error groupsSentry
- LogicFilter to groups linked to this PR's commits
- LogicCluster matched groups by root cause
- ActionWrite regression brief for the changeOpenAI
- OutputComment brief on the originating PRGitHub
What it does
Closes the loop between a merged change and the errors it caused. After a PR's release deploys, it waits for Sentry to surface new error groups in that release, clusters them by root-cause signature, and posts a regression brief as a comment on the exact PR, so the author sees the fallout where they merged.
When to use it
When you want post-merge accountability without the author hunting through Sentry. Ideal for teams that practice trunk-based development and want fast feedback attached to the change itself.
How it works
- 1A GitHub pull-request-merged webhook fires and records the release tag.
- 2After a settle delay, fetch Sentry error groups first seen in that release.
- 3Filter to groups whose suspect commits trace back to this PR.
- 4Cluster the matched groups by root-cause signature.
- 5An LLM writes a concise brief: what regressed and the likely line of cause.
- 6Post the brief as a comment on the originating GitHub PR.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SentryErrors, performance, releases.
- 3Connect OpenAIModels, embeddings, files.
- 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 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.