lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
41 lines
822 B
Markdown
41 lines
822 B
Markdown
---
|
|
name: data lineage
|
|
---
|
|
|
|
# /data lineage - Data Lineage Visualization
|
|
|
|
## Skills to Load
|
|
- skills/lineage-analysis.md
|
|
- skills/mcp-tools-reference.md
|
|
- skills/visual-header.md
|
|
|
|
## Visual Output
|
|
|
|
Display header: `DATA-PLATFORM - Lineage`
|
|
|
|
## Usage
|
|
|
|
```
|
|
/data lineage <model_name> [--depth N]
|
|
```
|
|
|
|
## Workflow
|
|
|
|
1. **Get lineage data**: Use `dbt_lineage` for dbt models
|
|
2. **Build lineage graph**: Identify upstream sources and downstream consumers
|
|
3. **Visualize**: ASCII tree with depth levels (see `skills/lineage-analysis.md`)
|
|
4. **Report**: Full dependency chain and refresh implications
|
|
|
|
## Examples
|
|
|
|
```
|
|
/data lineage dim_customers
|
|
/data lineage fct_orders --depth 3
|
|
```
|
|
|
|
## Required MCP Tools
|
|
|
|
- `dbt_lineage` - Get model dependencies
|
|
- `dbt_ls` - List dbt resources
|
|
- `dbt_docs_generate` - Generate full manifest
|