AI & RAG

Slack Q&A Bot Over MR History and ADRs

Lets reviewers ask a Slack bot why a piece of architecture is the way it is, and answers with citations drawn from past GitLab MR descriptions and Confluence ADRs.

CategoryAI & RAG
Enginepaperclip
Difficultyintermediate
Triggerchat
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerReviewer mentions bot in SlackSlack
  • ActionSearch MR descriptions for contextGitLabGitLab
  • ActionSearch ADR libraryConfluenceConfluence
  • ActionSynthesize cited answer (refuse if unsupported)OpenAI
  • OutputReply in Slack thread with sourcesSlack

What it does

Reviewers often need the story behind a design before they can approve a change. This chat bot answers free-form questions like "why do we use the outbox pattern for events?" by retrieving across two grounded sources: historical GitLab MR descriptions and the ADR library in Confluence. It replies in-thread with a synthesized answer plus links to the exact MRs and decisions it relied on, and says so plainly when no source covers the question.

When to use it

Use it to cut interrupt-driven "does anyone remember why..." pings to senior engineers. It turns institutional memory scattered across MRs and ADRs into a self-serve, cited answer.

How it works

  1. 1A reviewer mentions the bot in Slack with a question.
  2. 2The flow searches GitLab MR descriptions and Confluence ADRs for relevant passages.
  3. 3An OpenAI call synthesizes an answer strictly from retrieved passages, refusing to guess.
  4. 4The bot replies in the Slack thread with the answer and source links.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SlackChannels, DMs, threads, mentions.
  2. 2
    Connect GitLabRepos, MRs, pipelines, registry.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  4. 4
    Connect OpenAIModels, embeddings, files.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.