
Why Buster?
Data engineering with dbt involves countless repetitive tasks that require context about your data, code, and infrastructure:- Documentation Drift — dbt models change, but documentation falls behind. Manual updates are tedious and error-prone.
- Code Review Overhead — PRs need checks for performance issues, breaking changes, naming conventions, test coverage.
- Schema Changes — Upstream schema changes require updating staging models, propagating to marts, updating tests.
- Data Quality Monitoring — Regular checks for freshness, null rates, anomalies, referential integrity.
Simple Agent Example
Agents are YAML files committed to your repository. Unlike traditional scripts where you write procedural code, agents are declarative—you describe what you want accomplished in natural language. Here’s a complete agent:- Triggers — When the agent runs:
pull_request,scheduled,event, ormanual - Tools — What the agent can do:
safe(read-only),standard(read/write), orunrestricted(full access including bash) - Prompt — Your instructions in natural language describing what to accomplish