AI & RAG
Pull request runbook gap detector
On each opened PR, checks whether the changed code is covered by an existing runbook page and comments on the PR when a procedure is missing or its citation has gone stale.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened webhook with changed filesGitHub
- LogicFilter to operationally significant code paths
- ActionMatch paths against runbook vector index in PostgresPostgres
- LogicClassify each path as covered, stale, or undocumentedOpenAI
- OutputPost consolidated doc-gap comment on the PRGitHub
What it does
Closes the loop between code and docs at review time. When a PR touches operationally significant paths, it asks the runbook index whether a matching procedure exists, and if the docs are missing or outdated it leaves an actionable comment on the PR so the author fixes it before merge.
When to use it
Use it to enforce docs-as-you-go on critical services, when reviewers routinely forget to check that runbooks keep pace with shipping code and you want the reminder to land directly in the PR.
How it works
- 1A GitHub PR-opened webhook delivers the changed file list.
- 2A filter keeps only paths mapped to operational concerns (deploy, migrations, infra).
- 3Each in-scope path is matched against the runbook vector index in Postgres to find covering pages.
- 4A decision step classifies each path as covered, stale, or undocumented using OpenAI plus the page's freshness stamp.
- 5The workflow posts a single consolidated review comment on the PR listing gaps and stale citations to address.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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.