This hub covers automating dbt documentation: from scaffolding tools through AI generation, business context enrichment, and CI enforcement. As of early 2026, the toolchain handles these as separate concerns rather than a single tool. AI tools also read schema descriptions to generate code — poor documentation degrades AI output downstream.
Prerequisites
- A dbt project (Core or Cloud) with models in production
- Familiarity with schema.yml structure and dbt documentation basics
- For the Claude Code notes: Claude Code installed and a configured CLAUDE.md
Reading Order
The notes follow the natural progression of building a documentation pipeline:
-
dbt Documentation Scaffolding Tools — Start here. dbt-codegen generates YAML skeletons, dbt-osmosis propagates existing descriptions through your DAG. Together they can double coverage without writing a single new description.
-
AI Tools for dbt Documentation — Compare dbt Copilot, Claude Code with MCP, and Altimate AI for the description-writing step. Includes what all AI tools get wrong and how to build a feedback loop.
-
RAG for dbt Documentation — The key insight: all AI tools describe what the SQL does, not what the data means. RAG scoped to internal knowledge bases bridges that gap. Includes the simpler CLAUDE.md workaround for smaller teams.
-
dbt Documentation CI Enforcement — Prevent backsliding with dbt-coverage, dbt-checkpoint, dbt-score, and dbt-bouncer. Layer pre-commit hooks and CI checks to keep documentation coverage from eroding.
Related Notes
For the specific Claude Code workflow (codegen + AI, docs blocks, Mermaid lineage diagrams), see dbt Documentation with Claude Code. That note covers the hands-on “how do I document a model right now” pattern; this hub covers the broader “how do I build a documentation system” question.
Entry Points by Coverage Level
- Under 50% coverage: start with dbt Documentation Scaffolding Tools — scaffolding and propagation can reach 60% in a day.
- 60%+ coverage: start with AI Tools for dbt Documentation to fill gaps.
- AI descriptions too generic: go directly to RAG for dbt Documentation.