dbt-preflightlisted

## Purpose Inspect a dbt change set before it ships: identify which assets changed, estimate downstream impact, detect likely gaps in testing, contracts, documentation, and YAML alignment, and recommend the narrowest safe validation path. Preflight is read-only — do not edit code unless explicitly asked. ## When to Use - Before opening a PR in an analytics repository - Reviewing someone else's dbt change - Assessing the risk of a change whose downstream impact is unclear ## Inputs - The change set (branch diff or working tree) - The dbt project, for lineage and selector queries ## Workflow 1. **Enumerate changed assets:** ```bash git diff --name-status origin/main...HEAD ``` Classify each change: models, snapshots, seeds, macros, tests, schema YAML, semantic models, metrics, saved queries, exposures or BI-facing assets. 2. **Estimate blast radius.** For each changed model, list downstream dependents: ```bash dbt ls --select <model>+ ``` If a production manifest is available, cover the whole change set at once: ```bash dbt ls --select state:modified+ --state <path-to-prod-artifacts> ``` 3. **Run the review checklist.** Check for: - model grain changes - renamed columns or breaking contract changes - missing or weakened tests - YAML not updated after model changes - metrics or semantic definitions drifting from prior meaning - high blast radius due to downstream dependencies - incremental logic changes - sna