What problem does it solve?
A dbt build can succeed while the model produces the wrong column shape — extra columns, missing columns, wrong order, or wrong types — causing equality and existence tests to fail downstream. This Skill enforces a mechanical diff between the actual materialized columns and the columns declared in schema.yml or _models.yml before any model task is declared complete.
Core Features & Use Cases
- Column Contract Verification: Runs
altimate-dbt schema-verify --model <name> to produce a structured JSON verdict (match, mismatch, or no-spec) with four diff buckets: columns_extra, columns_missing, columns_reordered, and type_mismatches.
- Mechanical Fix Guidance: Maps each diff bucket to a concrete SQL action — remove, add, reorder, or cast columns in the SELECT — then rebuild and re-verify until the verdict is
match.
- Manual Fallback: When the altimate-dbt CLI is unavailable, it describes how to diff expected columns from YAML specs against
dbt show --select <name> --limit 0 output by hand.
- Use Case: After refactoring a CTE into its own intermediate model, run schema-verify on every touched model to catch a silently dropped column before equality tests fail in CI.
Quick Start
Ask the agent to run altimate-dbt schema-verify on the dbt model you just built and fix any reported column mismatches.