What problem does it solve? Cutting a release involves drafting a changelog from merged work, choosing the correct SemVer bump, and tagging in the right order — doing these out of sequence or guessing the version publishes a tag nobody actually chose. This Skill enforces the correct sequence with human confirmation at the critical points. ## Core Features & Use Cases - Changelog drafting: Gathers merged PRs and commits since the last tag, classifies them into Keep a Changelog buckets (Added/Changed/Fixed/Removed/Security), and summarizes dependency bumps into a single line. - Human-confirmed versioning: Uses an explicit question to confirm PATCH, MINOR, or pre-release bumps — never infers a version silently, and treats the first release as v0.1.0. - Gated tag and push: Validates CHANGELOG.md with a structural gate script before committing, tagging, and pushing to trigger the oss-release.yml workflow that builds images and publishes the GitHub Release. - Use Case: After merging a sprint of features, ask what changed since the last tag, review the drafted changelog, confirm a MINOR bump to v0.3.0, and push the tag to publish the release. ## Quick Start Ask the assistant to cut a release for the current repository and walk through drafting the changelog, confirming the version, and pushing the tag.
