Files
leo-claude-mktplace/plugins/ops-release-manager/commands/release-setup.md
lmiranda 2d51df7a42 feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]
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>
2026-02-06 14:52:11 -05:00

1.9 KiB

name, description
name description
release setup Detect version locations, release conventions, and configure release workflow

/release setup

Setup wizard for release management. Detects existing version locations and release conventions.

Visual Output

+----------------------------------------------------------------------+
|  RELEASE-MANAGER - Setup                                              |
+----------------------------------------------------------------------+

Skills to Load

  • skills/version-detection.md

Process

  1. Detect Version Locations

    • Scan for version strings in standard files:
      • package.json (Node.js)
      • pyproject.toml (Python)
      • setup.cfg, setup.py (Python legacy)
      • Cargo.toml (Rust)
      • marketplace.json (Claude plugins)
      • README.md title line
      • CHANGELOG.md header
    • Record each location with current version value
  2. Check Version Consistency

    • Compare all detected versions
    • Flag any mismatches between files
    • Identify the "source of truth" file
  3. Detect Release Conventions

    • Git tags: check git tag for existing pattern (v1.0.0 vs 1.0.0)
    • Branching: check for release/* branches
    • Changelog format: detect Keep a Changelog vs other
    • CI/CD: check for release workflows in .github/workflows or .gitlab-ci.yml
  4. Present Configuration

    • Show detected settings
    • Ask user to confirm or override
    • Store preferences for future commands

Output Format

## Release Configuration

### Version Locations
| File | Current Version | Pattern |
|------|----------------|---------|
| package.json | 2.3.1 | "version": "X.Y.Z" |
| README.md | 2.3.1 | # Project - vX.Y.Z |
| CHANGELOG.md | 2.3.1 | ## [X.Y.Z] - YYYY-MM-DD |

### Conventions
- Tag format: vX.Y.Z
- Branch pattern: release/X.Y.Z
- Changelog: Keep a Changelog format
- Source of truth: package.json

### Status: Ready
All versions in sync. Release workflow configured.