datalineage-bigquery-asset-impact-analysis

Analyze downstream impact of BigQuery asset changes using Data Lineage API.

Updated Jul 4, 2026
One-click install
npx skills add https://github.com/ssmleo/govfolio --skill datalineage-bigquery-asset-impact-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datalineage-bigquery-asset-impact-analysis
Source: https://github.com/ssmleo/govfolio/tree/main/.agents/skills/datalineage-bigquery-asset-impact-analysis
Command: npx skills add https://github.com/ssmleo/govfolio --skill datalineage-bigquery-asset-impact-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify the downstream impact of changes to BigQuery tables or views, preventing data disruptions and ensuring data integrity.

Core Features & Use Cases

  • Impact Analysis: Assess the consequences of modifying, deleting, or pausing updates to a BigQuery asset.
  • Downstream Dependency Identification: Determine all downstream tables, dashboards, and processes affected by a change.
  • Use Case: Before modifying a critical BigQuery table, use this Skill to understand the potential impact on dependent systems and plan accordingly.

Quick Start

Analyze the impact of changes to the BigQuery table 'my-prod-project.analytics.orders' using the datalineage skill.

Frequently Asked Questions about datalineage-bigquery-asset-impact-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze the downstream impact of changes to a BigQuery table?

This Skill performs BigQuery asset impact analysis by retrieving lineage information through the Google Cloud Data Lineage API to identify downstream dependencies and prevent data disruptions.

What is a BigQuery blast radius analysis for data lineage?

BigQuery blast radius analysis identifies all downstream tables, dashboards, and processes affected by modifying or deleting a specific asset, ensuring data integrity by mapping data lineage dependencies before applying changes.

Do I need the Google Cloud Data Lineage API to check BigQuery dependencies?

Yes, checking BigQuery dependencies requires access to the Google Cloud Data Lineage API and an active client connection to the Data Lineage MCP Server to retrieve downstream lineage information and perform impact analysis.

How do I find downstream tables and dashboards affected by a BigQuery schema change?

You find downstream tables and dashboards by running an impact analysis that maps data lineage to reveal the full blast radius of dependent systems, preventing data disruptions caused by modifying critical BigQuery tables or views.

Can I use this Skill to prevent data disruptions when pausing BigQuery table updates?

Yes, you can use this Skill to prevent data disruptions when pausing BigQuery table updates by assessing the consequences on downstream assets, identifying affected tables and dashboards to help you plan accordingly.

What is the best way to ensure data integrity before modifying a critical BigQuery view?

The best way to ensure data integrity before modifying a critical BigQuery view is to perform downstream dependency identification, assessing the blast radius of the change to prevent breaking dependent processes and systems.