SUMMARIZATION
Agent-built release narrative across services
On demand for a given release tag, an agent gathers Sentry errors and the GitHub commits that shipped across multiple services.
How it runs
The automated pipeline, trigger to output.
- TriggerManual run with a release tag
- ActionGather new and regressed Sentry issuesSentry
- ActionPull GitHub commits and PRs per serviceGitHub
- LogicCorrelate each error class to a likely commit
- OutputPost the per-service narrative to SlackSlack
What it does
This is an agent-driven investigation for releases that span several repos at once. Given a release tag, the agent collects the new and regressed Sentry error classes for the window, reads the GitHub commits and PRs that shipped in each affected service, and reasons about which change most likely caused each error. It produces a per-service narrative connecting symptoms to probable code changes.
When to use it
Use it for coordinated multi-service releases where a single error could originate in any of several deploys and a flat error list is not enough. The agent does the cross-referencing a human would otherwise do by hand across tabs.
How it works
A manual run is started with the release tag. The agent queries Sentry for new and regressed issues in the window, then pulls the relevant GitHub commit and PR history per service. It correlates each error class to the most plausible commit, summarizing its confidence and reasoning. It assembles a per-service release-health narrative with linked issues and commits, and posts the finished note to Slack for the release owners.
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 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.