AI & RAG

Alert Reviewers When a Diff Contradicts an ADR

Scans newly pushed merge requests, and when the change appears to violate a recorded architecture decision, sends the assigned reviewers a Slack alert quoting the conflicting ADR.

CategoryAI & RAG
Enginesim
Difficultyadvanced
Triggerevent
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitLab MR push eventGitLabGitLab
  • ActionPull diff and changed filesGitLabGitLab
  • ActionRetrieve governing ADRsConfluenceConfluence
  • ActionJudge diff against ADR rationaleOpenAI
  • LogicExit if no conflict detected
  • OutputDM reviewers with violated ADR clauseSlack

What it does

This is a guardrail, not a summarizer. On each new or updated MR it retrieves the ADRs touching the changed areas and asks whether the diff contradicts any accepted decision (for example, introducing a banned dependency or bypassing an agreed boundary). Only when a likely conflict is found does it notify the MR's assigned reviewers in Slack, with the exact ADR clause and the offending file.

When to use it

Use it when silent architecture drift is your real risk and you do not want yet another always-on bot comment. It stays quiet on compliant MRs and speaks only when a decision looks violated.

How it works

  1. 1A GitLab webhook fires on merge_request push.
  2. 2The flow gathers the diff and changed file paths.
  3. 3Relevant ADRs are retrieved from Confluence.
  4. 4An OpenAI call judges conflict vs. no-conflict and extracts the violated clause.
  5. 5A logic branch exits silently when no conflict is found.
  6. 6On conflict, a Slack DM goes to the MR reviewers with the citation and a jump link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitLabRepos, MRs, pipelines, registry.
  2. 2
    Connect ConfluenceSpaces, pages, blueprints.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  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.