personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(commands): wire dispatch files to real sub-command names via Skill tool

Browse Source 
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>
This commit is contained in:
Leo Miranda
2026-02-08 21:04:24 -05:00
parent 93d93fcf09
commit 5bbcee06ac
27 changed files with 536 additions and 286 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
plugins/projman/commands/rfc.md
View File

@@ -16,7 +16,7 @@ agent: planner
Manage the full RFC lifecycle through sub-commands. RFCs provide a structured way to document, discuss, and approve changes before implementation.
When invoked without a sub-command, display available actions and ask which to run.
When invoked without a sub-command or with `$ARGUMENTS`, handle sub-commands inline using the documentation below.
## Invocation
@@ -34,11 +34,19 @@ When invoked without a sub-command, display available actions and ask which to r
| `approve` | `/rfc approve <number>` | Approve RFC in Review status |
| `reject` | `/rfc reject <number>` | Reject RFC with documented reason |
## Workflow
## Routing
1. Display the table above
If `$ARGUMENTS` is provided (e.g., user typed `/rfc create`):
1. Match the first word of `$ARGUMENTS` against the Command column above
2. Execute the corresponding sub-command using the inline documentation below
3. Pass any remaining arguments to the sub-command handler
If no arguments provided:
1. Display the Available Commands table
2. Ask: "Which command would you like to run?"
3. Route to the selected sub-command
3. When the user responds, execute the matching sub-command using the inline documentation below
**Note:** RFC commands are handled inline in this file - there are no separate command files to invoke.
---