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>
821 B
821 B
name
| name |
|---|
| data explain |
/data explain - dbt Model Explanation
Skills to Load
- skills/dbt-workflow.md
- skills/lineage-analysis.md
- skills/mcp-tools-reference.md
- skills/visual-header.md
Visual Output
Display header: DATA-PLATFORM - Model Explanation
Usage
/data explain <model_name>
Workflow
- Get model info: Use
dbt_lineagefor metadata (description, tags, materialization) - Analyze dependencies: Show upstream/downstream as tree
- Compile SQL: Use
dbt_compileto get rendered SQL - Report: Purpose, materialization, dependencies, key SQL logic
Examples
/data explain dim_customers
/data explain fct_orders
Required MCP Tools
dbt_lineage- Get model dependenciesdbt_compile- Get compiled SQLdbt_ls- List related resources