AI & RAG
On config-change PRs, post the original rationale as a review comment
When a merge request touches a config file, this workflow finds the prior rationale for each changed key from Git history and ADRs and posts it as a review comment so reviewers…
How it runs
The automated pipeline, trigger to output.
- TriggerMerge request touches a watched config fileGitLab
- LogicExtract the specific config keys/lines changed
- ActionPull introducing commit + message for each lineGitLab
- ActionRetrieve matching ADRs from ConfluenceConfluence
- ActionCompose per-key rationale with citations
- OutputPost rationale as an MR review commentGitLab
What it does
Every time someone opens a merge request that edits a config file, it surfaces the historical rationale for each line being changed and posts it directly on the MR. Reviewers no longer approve a one-line value bump without knowing the original decision behind it.
When to use it
When config changes ship too easily and reviewers lack context. Ideal for repos where load-bearing values (timeouts, limits, feature flags) are casually edited and the reasoning lives in old commits or ADRs nobody reopens.
How it works
- 1A GitLab merge-request event fires when the diff touches a watched config path.
- 2A logic step extracts the specific keys/lines that changed.
- 3For each changed line, the agent pulls the introducing commit and message from Git history.
- 4It retrieves any ADR in Confluence referenced by that commit or matching the key.
- 5It composes a per-key "original rationale" summary with citations.
- 6It posts the summary as a single MR review comment for the reviewer.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 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 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.