AI & RAG
PR Design-Compliance Check Against Confluence RFCs
On every pull request, retrieves the governing RFC from Confluence, compares the diff against the documented design decisions.
How it runs
The automated pipeline, trigger to output.
- TriggerPull request opened or updatedGitHub
- ActionMatch changed files to governing RFC chunksSupabase
- LogicSkip if no governing RFC mapped
- ActionCompare diff vs RFC decisions, emit findingsOpenAI
- OutputPost GitHub review comment with RFC citationsGitHub
What it does
Guards architectural intent at review time. When a PR opens, the flow finds the RFC that governs the touched code, then checks the diff against that RFC's stated decisions and constraints. It posts a GitHub review comment calling out any deviation, each backed by a link to the specific RFC section it conflicts with.
When to use it
When teams approve RFCs but drift from them in implementation, or when reviewers can't recall every design constraint. Best for repos with a clear RFC-to-component mapping.
How it works
- 1A GitHub pull_request event triggers the flow.
- 2Changed file paths are matched to the relevant RFC chunks in the Supabase vector store.
- 3A logic gate skips PRs whose files map to no governing RFC.
- 4OpenAI compares the diff against the retrieved RFC decisions and emits structured findings with citation anchors.
- 5The bot posts a GitHub review comment listing each deviation linked to its RFC section, or an approving note if none are found.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SupabaseTables, auth, storage, edge functions.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect ConfluenceSpaces, pages, blueprints.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.