
from signalpilot467
Guidance and rules for adding versioned dbt models (v2, latest_version, versions: YAML and ref() usage) to avoid creating standalone duplicate models.
Provides concrete, opinionated best-practices for adding versioned models in dbt (core 1.6+). It explains when to use the versions: YAML, how to name version SQL files, how ref() resolves versions, and verification steps to confirm both v1 and v2 nodes are registered. The instructions prevent common mistakes like creating separate _v2 models without proper YAML and recommend minimal-change v2 SQL patterns (select-from-ref) when appropriate.
Use this skill when a change request mentions creating a v2 of an existing model, making backward-compatible changes, or when you need to pin or change which model version upstream code references. It triggers for tasks mentioning 'v2', 'version', 'latest_version', 'defined_in', or dbt model ref() behavior.
has_scripts=false).dbt ls --select <model> --output json).Best suited for agents that can run shell/dbt commands (Bash/dbt). The guidance is implementation-focused and useful to any automation that authors dbt models or code changes.
This skill has not been reviewed by our automated audit pipeline yet.