Data Lineage

Track and visualize data flow across pipelines and ETL processes.

Updated Feb 13, 2026

Search Tags:#data flow #impact analysis #data lineage #schema change #data governance #pipeline tracking

Ready to run

npx skills add https://github.com/cdalsoniii/brightpath-coder --skill data-lineage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Data Lineage
Source: https://github.com/cdalsoniii/brightpath-coder/tree/main/.cursor/skills/data-lineage
Command: npx skills add https://github.com/cdalsoniii/brightpath-coder --skill data-lineage

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the complexity of understanding how data moves through various systems, enabling users to track data origins, transformations, and destinations.

Core Features & Use Cases

Data Flow Mapping: Visualizes the path data takes from source to destination.
Impact Analysis: Assesses the downstream effects of schema changes or pipeline modifications.
Use Case: When a schema change is proposed for a critical data table, this Skill can quickly identify all dependent pipelines and reports, allowing for proactive adjustments and preventing breakages.

Quick Start

Use the data lineage skill to trace the flow of data for the 'customer_orders' table.

Frequently Asked Questions about Data Lineage

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

FAQPage Schema

How do I trace data flow across ETL pipelines and track data origins?▼

To trace data flow across ETL pipelines, this Skill maps the path data takes from source to destination by reading pipeline configurations and CDC configurations, generating a comprehensive visual graph of data origins and transformations.

How does schema change impact analysis work for downstream data pipelines?▼

Schema change impact analysis works by scanning query logs and schema registries to identify all dependent pipelines and reports. This allows you to assess downstream effects proactively and prevent breakages before modifications are applied.

Do I need read access to specific configurations to visualize data lineage?▼

Yes, you need read access to pipeline configurations, schema registries, query logs, and CDC configurations. These sources are required to build a comprehensive lineage graph and accurately track data freshness.

What is the best way to monitor data freshness and track pipeline modifications?▼

The best way to monitor data freshness is by continuously tracking pipeline configurations and CDC logs. This approach visualizes data transformations from source to destination and highlights the downstream effects of any pipeline modifications.

Can I use this approach for impact analysis on critical data tables?▼

Yes, you can use this approach for impact analysis on critical data tables. When a schema change is proposed, it quickly identifies all dependent pipelines and reports, allowing for proactive adjustments and preventing breakages.