Files
leo-claude-mktplace/plugins/ops-release-manager/commands/release.md
lmiranda 5bbcee06ac fix(commands): wire dispatch files to real sub-command names via Skill tool
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>
2026-02-08 21:04:24 -05:00

1.6 KiB

name, description
name description
release Release management — type /release <action> for commands

/release

Release management with semantic versioning, changelog generation, and tag management.

When invoked without a sub-command, display available actions and ask which to run.

Available Commands

Action Command to Invoke Description
setup /ops-release-manager:release-setup Setup wizard — detect version locations and release conventions
prepare /ops-release-manager:release-prepare Prepare release: bump versions, update changelog, create branch
validate /ops-release-manager:release-validate Pre-release checks — verify versions, changelog, dependencies
tag /ops-release-manager:release-tag Create and push git tag with release notes
rollback /ops-release-manager:release-rollback Revert a release — remove tag, revert version bump
status /ops-release-manager:release-status Show current version and unreleased changes

Routing

If $ARGUMENTS is provided (e.g., user typed /release prepare):

  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., /ops-release-manager:release-prepare)