SUMMARIZATION
Summarize MR Thread into a Decision Rationale on Merge
When a GitLab merge request is merged, distills the full comment thread into a concise reviewer decision rationale and posts it back as a note on the merge record so the why…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR merged eventGitLab
- ActionFetch all MR discussion threads and notesGitLab
- LogicFilter out bot noise, +1s, and resolved nitpicks
- ActionDistill thread into decision rationaleOpenAI
- OutputPost rationale as pinned note on merge recordGitLab
What it does
When an MR is merged, this workflow reads the entire discussion thread, separates resolved concerns from open questions, and writes a short structured rationale (what was debated, what was decided, what was deferred) as a final note on the merge request. The merge record stops being a wall of back-and-forth and starts carrying a one-paragraph answer to "why did we ship this?".
When to use it
Use it on repos where reviews get noisy and the merge button gets clicked faster than the context is captured. Ideal for teams doing post-incident archaeology or onboarding new reviewers who need the decision, not the 40-comment scroll.
How it works
- 1GitLab merge event fires the trigger.
- 2The workflow fetches all discussion notes and threads on the MR.
- 3A logic step filters out bot noise, +1s, and resolved nitpicks.
- 4OpenAI distills the remaining substance into a rationale: concerns raised, resolutions, and any deferred follow-ups.
- 5The rationale is posted back as a pinned note on the merged MR.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect OpenAIModels, embeddings, files.
- 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 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.