
Tracing Downstream Lineage
Before you drop a column or refactor a DAG, this traces what downstream tables, dashboards, and ML models will break. It walks you through building a dependency tree by searching DAG source code, querying information schema for dependent views, and categorizing impact by criticality (production dashboards versus ad hoc analyst queries). The output is an impact report with a visual diagram, stakeholder list, and specific migration tasks. If you're on Astro, the Lineage tab does some of this automatically, but this skill gives you the systematic checklist for when you need to assess blast radius manually. Basically prevents the "I changed one table and now three teams are pinging me" scenario.
- skills.sh installs
- 1.1K
- GitHub stars
- 459
- last updated
- Aug 21, 2026
Install
$ npx -y skills add astronomer/agents --skill tracing-downstream-lineage --agent claude-codeInstalls into .claude/skills of the current project.
Files
Downstream Lineage: Impacts
Answer the critical question: "What breaks if I change this?"
Use this BEFORE making changes to understand the blast radius.
Impact Analysis
Step 1: Identify Direct Consumers
Find everything that reads from this target:
For Tables:
-
Search DAG source code: Look for DAGs that SELECT from this table
- Use
af dags listto get all DAGs - Use
af dags source <dag_id>to search for table references - Look for:
FROM target_table,JOIN target_table
- Use
-
Check for dependent views:
-- Snowflake SELECT * FROM information_schema.view_table_usage WHERE table_name = '<target_table>' -- Or check SHOW VIEWS and search definitions -
Look for BI tool connections:
- Dashboards often query tables directly
- Check for common BI patterns in table naming (rpt_, dashboard_)
On Astro
If you're running on Astro, the Lineage tab in the Astro UI provides visual dependency graphs across DAGs and datasets, making downstream impact analysis faster. It shows which DAGs consume a given dataset and their current status, reducing the need for manual source code searches.
For DAGs:
Sponsors
Details
- Repository
- github.com/astronomer/agents
- Category
- Automation & Workflows
- First seen
- Apr 16, 2026
More from astronomer/agents
All 24- Checking Freshness1K
- Annotating Task Lineage1K
- Cosmos Dbt Core990
- Airflow Hitl980
- Creating Openlineage Extractors960
- Cosmos Dbt Fusion925
- Warehouse Init841
- Deploying Airflow817
- Troubleshooting Astro Deployments655
- Airflow Plugins622
- Managing Astro Deployments595
- Blueprint584
- Init176
- Managing Astro Local Env1.6K
- Airflow1.5K
- Analyzing Data1.4K
- Authoring Dags1.3K
- Debugging Dags1.2K
- Testing Dags1.2K
- Migrating Airflow 2 To 31.1K
- Setting Up Astro Project1.1K
- Tracing Upstream Lineage1.1K
- Profiling Tables1.1K