lmiranda
2d51df7a42
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>
1.2 KiB
1.2 KiB
Release Manager Integration
Add to your project's CLAUDE.md:
Release Management
This project uses ops-release-manager for versioning and release automation.
Commands
/release setup- Detect version locations and configure release workflow/release status- Show current version and unreleased changes/release prepare <major|minor|patch>- Bump versions and update changelog/release validate- Pre-release checks before tagging/release tag- Create annotated git tag with release notes/release rollback- Revert a release if needed
Versioning
- Follows SemVer (MAJOR.MINOR.PATCH)
- Version locations: package.json, README.md, CHANGELOG.md (auto-detected)
- Changelog follows Keep a Changelog format
Release Process
- All changes documented under
[Unreleased]in CHANGELOG.md - Run
/release prepare minor(or major/patch) when ready - Run
/release validateto verify readiness - Run
/release tag --pushto finalize
Conventions
- Tag format:
vX.Y.Z(annotated tags with release notes) - Branch format:
release/X.Y.Z(for major/minor releases) - Commit message:
chore(release): prepare vX.Y.Z