AI & RAG
Ground MR Review Comments in ADR Rationale
When a GitLab merge request is opened, retrieves the most relevant architecture decision records and posts a review comment that cites which decisions the change touches and why.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or updatedGitLab
- ActionFetch MR description and changed pathsGitLab
- ActionRetrieve candidate ADR docsConfluence
- ActionSelect relevant ADRs and draft cited summaryOpenAI
- OutputPost grounded review comment to MRGitLab
What it does
Every time a merge request is opened or updated, this bot reads the MR title, description, and changed file paths, then searches your ADR corpus for the decisions most relevant to the change. It posts a single grounded review comment that names the specific ADRs in play, quotes the rationale behind each, and flags where the diff appears to diverge from a recorded decision.
When to use it
Use it on repos where architecture decisions are documented as ADRs but reviewers keep re-litigating settled questions. It gives every reviewer the decision context up front instead of forcing them to dig through wiki history.
How it works
- 1A GitLab webhook fires on merge_request open/update.
- 2The flow pulls the MR description and changed paths from the GitLab API.
- 3ADR documents are fetched from Confluence and embedded for retrieval.
- 4An OpenAI call selects the top decisions and drafts a citation-backed summary, including any apparent divergence.
- 5The comment is posted back to the MR thread with linked ADR references.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect OpenAIModels, embeddings, files.
- 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 AI & RAG workflows
Publish a Grounded API FAQ Page to Confluence Weekly
Each week, clusters the top unanswered or repeated API questions, generates spec-grounded answers with citations.
Detect Breaking API Changes from Spec Diffs and Alert Owners
Compares the new OpenAPI spec against the previous version on each GitLab merge, uses retrieval over the changelog to classify whether changes are breaking.
Pre-meeting prep brief grounded in Coda and CRM
Before each booked sales meeting, builds a one-page prep brief by combining the account's HubSpot context with grounded talking points and objection responses pulled from your…
Coda-grounded sales answer bot with citations in Slack
Reps ask product, pricing, or competitive questions in Slack and get an answer drawn only from your Coda knowledge hub, with links to the exact docs and rows it pulled from.
Weekly knowledge-gap digest from unanswered rep questions
Each week, scans rep questions the answer bot couldn't ground in Coda, clusters the recurring gaps.
RFP and security questionnaire drafter grounded in Coda
Drafts answers to inbound RFP and security questionnaire questions by retrieving approved language from your Coda hub, then files the cited draft for review before a rep sends it.
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.