release

To automate git tagging and release notes generation, the Skill creates annotated vX.Y.Z tags and groups commits since the last tag into accurate notes, especially when conventional commits are detected. It requires a clean working tree preflight before applying any version bump.

Yes, the release workflow supports versioning across Node, Python, Rust, plain VERSION files, and Claude Code plugin marketplaces. It performs deterministic manifest and lockfile updates by detecting and bumping the correct project manifest format automatically.

The best way to ensure shippability is using the production mode quality gate, which runs the full check-pr-readiness gauntlet against the specific release range. This verifies code quality before computing and applying the next semver version.

To compute the next semver version, the Skill analyzes commits and applies mode-based risk control to determine the correct bump. You can explicitly request a patch or major bump, or let it detect the appropriate semantic version automatically.

Yes, you can control when the annotated git tag gets pushed because the Skill creates the local commit and tag, then stops before any push. It requires explicit user authorization before publishing the tag to the remote repository.

You need a clean working tree before starting the versioning process to prevent shipping uncommitted or untested changes. The preflight check ensures the branch is correct and the repository state is identifiable before applying quality gates.