Add single-line visual headers to 66 command files across 10 plugins: - clarity-assist (2 commands): 💬 - claude-config-maintainer (5 commands): ⚙️ - cmdb-assistant (11 commands): 🖥️ - code-sentinel (3 commands): 🔒 - contract-validator (5 commands): ✅ - data-platform (10 commands): 📊 - doc-guardian (5 commands): 📝 - git-flow (8 commands): 🔀 - pr-review (7 commands): 🔍 - viz-platform (10 commands): 🎨 Each command now displays a consistent header at execution start: ┌────────────────────────────────────────────────────────────────┐ │ [icon] PLUGIN-NAME · Command Description │ └────────────────────────────────────────────────────────────────┘ Addresses #275 (other plugin commands visual output) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.8 KiB
1.8 KiB
/lineage - Data Lineage Visualization
Visual Output
When executing this command, display the plugin header:
┌──────────────────────────────────────────────────────────────────┐
│ 📊 DATA-PLATFORM · Lineage │
└──────────────────────────────────────────────────────────────────┘
Then proceed with the visualization.
Show data lineage for dbt models or database tables.
Usage
/lineage <model_name> [--depth N]
Workflow
-
Get lineage data:
- Use
dbt_lineagefor dbt models - For database tables, trace through dbt manifest
- Use
-
Build lineage graph:
- Identify all upstream sources
- Identify all downstream consumers
- Note materialization at each node
-
Visualize:
- ASCII art dependency tree
- List format with indentation
- Show depth levels
-
Report:
- Full dependency chain
- Critical path identification
- Refresh implications
Examples
/lineage dim_customers
/lineage fct_orders --depth 3
Output Format
Sources:
└── raw_customers (source)
└── raw_orders (source)
dim_customers (table)
├── upstream:
│ └── stg_customers (view)
│ └── raw_customers (source)
└── downstream:
└── fct_orders (incremental)
└── rpt_customer_lifetime (table)
Available Tools
Use these MCP tools:
dbt_lineage- Get model dependenciesdbt_ls- List dbt resourcesdbt_docs_generate- Generate full manifest