The problem it solves
A small dbt change can affect downstream marts, dashboards, and business processes. Teams need to know what depends on a model or column before merging changes.
What it does
Identifies downstream models and consumers.
Uses dbt graph context and column-level lineage.
Summarizes affected columns and risky dependencies.
Helps reviewers understand blast radius before merge.
When to use it
BEFORE
changing a shared staging or intermediate model
WHEN
renaming or removing columns
DURING
dbt refactors
WHEN
assessing change risk in a pull request
How it works
The skill locates the changed model, maps the dbt dependency graph, traces lineage, and reports downstream impact.
Put This Skill to Work. On Your Own dbt Project.
Install Altimate Code, connect your warehouse and call the skill from your terminal or your IDE. Book a demo to see it run on a project like yours.
