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>
1.7 KiB
1.7 KiB
name, description
| name | description |
|---|---|
| deploy | Deployment management — type /deploy <action> for commands |
/deploy
CI/CD deployment pipeline management for Docker Compose and self-hosted infrastructure.
When invoked without a sub-command, display available actions and ask which to run.
Available Commands
| Action | Command to Invoke | Description |
|---|---|---|
setup |
/ops-deploy-pipeline:deploy-setup |
Interactive setup wizard for deployment configuration |
generate |
/ops-deploy-pipeline:deploy-generate |
Generate docker-compose.yml, Caddyfile, and systemd units |
validate |
/ops-deploy-pipeline:deploy-validate |
Validate deployment configs for correctness and best practices |
env |
/ops-deploy-pipeline:deploy-env |
Manage environment-specific config files (.env.development, .env.production) |
check |
/ops-deploy-pipeline:deploy-check |
Pre-deployment health check (disk, memory, ports, DNS, Docker) |
rollback |
/ops-deploy-pipeline:deploy-rollback |
Generate rollback plan for a deployment |
Routing
If $ARGUMENTS is provided (e.g., user typed /deploy generate):
- Match the first word of
$ARGUMENTSagainst the Action column above - Invoke the corresponding command from the "Command to Invoke" column using the Skill tool
- Pass any remaining arguments to the invoked command
If no arguments provided:
- Display the Available Commands table
- Ask: "Which action would you like to run?"
- 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., /ops-deploy-pipeline:deploy-generate)