What problem does it solve?
This skill turns a messy “we shipped changes—what version is next?” moment into a consistent, safe GitHub release process with correct semantic versioning and reader-ready release notes.
Core Features & Use Cases
- Version decision from Conventional Commits: Determines the next semantic version by scanning non-merge commits since the last tag and selecting the highest-impact bump, including prerelease behavior.
- Release notes drafting: Produces GitHub release notes using either auto-generated notes (via the release workflow config) or curated notes (grouped by change type), with optional highlights and upgrade notes for breaking changes.
- Tagging and publishing ceremony: Creates and pushes an annotated tag, then publishes the GitHub release (or defers to a tag-driven workflow if present), followed by verification and a clear report of what happened.
Quick Start
Run the /release skill when your work is merged to the default branch to compute the next version, draft the notes, tag the commit, and publish the GitHub release.