Click any tag below to further narrow down your results
Links
dbt-doctor scans dbt projects for maintainability issues like missing documentation, weak test coverage, schema drift risks, and DAG problems. It generates a health score (0–100) and can run locally, in pre-commit hooks, or as a GitHub Actions quality gate.
- Detects 122 rules across 9 categories including missing docs/tests, stale models, naming convention violations, and governance gaps
- Integrates into CI/CD with GitHub Actions, outputs sticky PR comments, and can fail builds based on error/warning thresholds
- Configurable via presets (default/strict/enterprise), inline suppressions, and .dbt-doctor config file; respects .gitignore and .sqlfluff rules
Claire Gouze lays out a practical process to build and test a context layer your data agents can trust. She shows how to start small with dbt docs and markdown files, write evals, clean up data models, and iterate until you reach around 90% reliability.
- Adding query logs and profiling alone got the agent stuck around 40% accuracy; reworking the data model and documentation pushed it to 90%.
- Treat context like code: store it in files/markdown, version in Git, add CI/CD evals, and iterate on failure cases rather than plugging agents directly into raw databases.
- Start small—10 to 20 core tables with existing dbt docs—rather than trying to cover the whole warehouse at once.
- Evals should come from real BI query history or autogenerated question sets, reviewed by teams and tracked over time to build trust in the agent.