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>
822 B
822 B
name
| 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
- Get lineage data: Use
dbt_lineagefor dbt models - Build lineage graph: Identify upstream sources and downstream consumers
- Visualize: ASCII tree with depth levels (see
skills/lineage-analysis.md) - 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 dependenciesdbt_ls- List dbt resourcesdbt_docs_generate- Generate full manifest