lmiranda
5bbcee06ac
All dispatch files referenced display names (e.g., `/doc audit`) that don't correspond to real slash commands. Claude Code resolves commands by filename, so `/doc audit` loads `doc.md` with $ARGUMENTS but never routes to `doc-audit.md`. Changes: - Updated 24 dispatch files with explicit Skill tool routing - Added "Command to Invoke" column with plugin-prefixed names - Added $ARGUMENTS matching for automatic routing - RFC dispatch file uses inline handling (no separate command files) - Updated COMMANDS-CHEATSHEET.md with invocation methods - Updated MIGRATION-v9.md with command name mapping explanation Affects: 25 dispatch files across 12 plugins (core, data, saas, ops, debug) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
41 lines
2.0 KiB
Markdown
41 lines
2.0 KiB
Markdown
---
|
|
name: data
|
|
description: Data engineering tools — type /data <action> for commands
|
|
---
|
|
|
|
# /data
|
|
|
|
Data engineering tools with pandas, PostgreSQL/PostGIS, and dbt integration.
|
|
When invoked without a sub-command, display available actions and ask which to run.
|
|
|
|
## Available Commands
|
|
|
|
| Action | Command to Invoke | Description |
|
|
|--------|-------------------|-------------|
|
|
| `ingest` | `/data-platform:data-ingest` | Load data from CSV, Parquet, JSON into DataFrame |
|
|
| `profile` | `/data-platform:data-profile` | Generate data profiling report with statistics |
|
|
| `schema` | `/data-platform:data-schema` | Explore database schemas, tables, columns |
|
|
| `explain` | `/data-platform:data-explain` | Explain query execution plan |
|
|
| `lineage` | `/data-platform:data-lineage` | Show dbt model lineage and dependencies |
|
|
| `lineage-viz` | `/data-platform:data-lineage-viz` | dbt lineage visualization as Mermaid diagrams |
|
|
| `run` | `/data-platform:data-run` | Run dbt models with validation |
|
|
| `dbt-test` | `/data-platform:data-dbt-test` | Formatted dbt test runner with summary |
|
|
| `quality` | `/data-platform:data-quality` | DataFrame quality checks |
|
|
| `review` | `/data-platform:data-review` | Comprehensive data integrity audits |
|
|
| `gate` | `/data-platform:data-gate` | Binary pass/fail data integrity gates |
|
|
| `setup` | `/data-platform:data-setup` | Setup wizard for data-platform MCP servers |
|
|
|
|
## Routing
|
|
|
|
If `$ARGUMENTS` is provided (e.g., user typed `/data ingest`):
|
|
1. Match the first word of `$ARGUMENTS` against the **Action** column above
|
|
2. **Invoke the corresponding command** from the "Command to Invoke" column using the Skill tool
|
|
3. Pass any remaining arguments to the invoked command
|
|
|
|
If no arguments provided:
|
|
1. Display the Available Commands table
|
|
2. Ask: "Which action would you like to run?"
|
|
3. When the user responds, invoke the matching command using the Skill tool
|
|
|
|
**Note:** Commands can also be invoked directly using their plugin-prefixed names (e.g., `/data-platform:data-ingest`)
|