SUMMARIZATION

Daily Slack Digest of Decision Rationales for Merged MRs

Once a day, distills the comment threads of every MR merged in the last 24 hours into one-line decision rationales and posts a single grouped digest to a Slack channel…

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule
  • ActionList MRs merged in the last 24 hoursGitLabGitLab
  • ActionFetch each MR discussion threadGitLabGitLab
  • ActionDistill each thread into a one-line rationaleOpenAI
  • LogicGroup by project; skip if nothing merged
  • OutputPost grouped decision digest to SlackSlack

What it does

Each morning this workflow gathers every merge request merged in the previous day, reads each thread, and distills it into a single-sentence rationale capturing what was decided and why. It then assembles all of them into one tidy Slack digest, grouped by project, so the team gets the day's shipped decisions without opening GitLab.

When to use it

Use it for teams that want async visibility into what merged and why, especially across multiple repos. It replaces the habit of scrolling activity feeds with a once-a-day readout aimed at leads and stakeholders.

How it works

  1. 1A daily schedule triggers the run.
  2. 2GitLab returns all MRs merged in the last 24 hours.
  3. 3For each MR, the workflow fetches its discussion thread.
  4. 4OpenAI distills every thread into a one-line rationale.
  5. 5A logic step groups the rationales by project and skips posting if nothing merged.
  6. 6The grouped digest is posted to the team Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.