REQUIRED before writing or modifying ANY dbt model. Invoke this skill FIRST
whenever a task says "create", "build", "add", "modify", "update", "fix", or
"refactor" a dbt model, staging file, mart, incremental, or snapshot.
Skipping this skill is the leading cause of silent-correctness bugs —
models that compile and `dbt build` cleanly but produce wrong values. It
contains the patterns that prevent the most common such bugs encountered
in real dbt projects:
• Incremental high-water marks (`>=` vs `>` ties → silent row dropout)
• Snapshot strategy selection (timestamp vs check, `unique_key` choice)
• `LEFT JOIN + COUNT(*)` phantom rows from unmatched parents
• Type harmonization in `COALESCE` / `CASE` / `UNION` legs
• Date-spine completeness (every period present, even empty ones)
• Off-by-one window boundaries (`BETWEEN d - (N-1) AND d` for N-wide)
• Uniqueness enforcement when schema implies a key
• Window-function `LIMIT` with deterministic tiebreaker
• Verifying transformation correctness with dbt unit tests, not just `dbt build`
• Enumerating every requested deliverable and checking each exists on disk
Do not start writing SQL until this skill is loaded. Powered by altimate-dbt.
☆750 repo stars⑂133 repo forks