What problem does it solve? Preparing a release involves tedious, error-prone work: picking the right version, summarizing changes since the last tag, updating changelogs, and tagging safely. This Skill standardizes that entire workflow so releases are consistent, user-facing, and never published from a dirty worktree. ## Core Features & Use Cases - Release Records: Create, update, review, or correct changelogs, GitHub Release drafts, and release summaries without tagging or publishing unless asked. - Version Selection: Follow the repository's existing versioning convention (SemVer or otherwise), falling back to SemVer-compatible CalVer (vYYYY.M.D) or Go-module-safe v0.YYYYMMDD.N when no convention exists. - Safe Tag & Publish: Require a clean worktree, commit changelog updates before tagging, create annotated tags, and push only with explicit authority. - Use Case: Ask for release notes since the last tag and receive grouped, user-facing notes (Breaking, Added, Fixed, Security) ready to paste into a GitHub Release, plus the exact commit ready to tag. ## Quick Start Prepare release notes for all changes since the previous tag and tell me which commit is ready to tag.
