What problem does it solve? Cutting a release by hand means reading the commit log, deciding a semver bump, writing a CHANGELOG entry, and opening a release PR — a repetitive, error-prone process that is easy to get wrong. ## Core Features & Use Cases - Automatic semver detection: Reads conventional commits since the last tag and proposes a MAJOR, MINOR, or PATCH bump, with an option to override. - Agent-generated CHANGELOG: Groups commits into Added, Fixed, Changed, and Breaking sections and prepends the entry to CHANGELOG.md after user review. - Release PR automation: Creates a release/vX.Y.Z branch, commits the changelog, pushes it, and opens a PR targeting main via the GitHub CLI. - Use Case: After merging several feature branches, run the skill with --dry-run to preview the proposed version and changelog, then execute it to open a release PR without touching git commands manually. ## Quick Start Ask the assistant to cut a new release from the current branch, for example by saying: run the release skill with --dry-run to preview the next version and changelog.