What problem does it solve? Cutting a release involves many error-prone manual steps: moving Unreleased changelog entries, picking the right SemVer bump, syncing manifest versions, and coordinating tags with CI. This Skill standardizes the entire release cut so nothing is forgotten and no version ships without a changelog entry. ## Core Features & Use Cases - Changelog-driven release cut: Moves ## [Unreleased] entries into a dated ## [X.Y.Z] section following Keep a Changelog, and updates comparison links. - SemVer bump proposal: Suggests major, minor, or patch based on the pending entries (breaking changes, Added/Changed, Fixed/Security) and asks for confirmation. - Manifest version sync: Updates the version in package.json, Cargo.toml, pyproject.toml, pubspec.yaml, and similar manifests, including lockfiles. - CI-aware tagging: Defers tag and GitHub release creation to the release.yml workflow on merge to main, with a manual fallback via gh release create when the workflow is inactive. - Hotfix flow: Supports patch releases cut directly from main on hotfix/* branches, including the required sync back to develop. - Use Case: Say "corta la versión 1.2.0" and the Skill verifies a clean tree, proposes the bump, rewrites the CHANGELOG, bumps the manifest, and commits on a chore/corte-v1.2.0 branch ready for PR. ## Quick Start Ask the assistant to cut a new release, for example: "Cut version 1.3.0 from the current Unreleased changelog entries."