release-version

Coordinate SemVer version bumps, changelogs, annotated Git tags, and release notes.

Updated May 6, 2026
One-click install
npx skills add https://github.com/korwlik23/skills --skill release-version-korwlik23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-version
Source: https://github.com/korwlik23/skills/tree/main/v1/release-version
Command: npx skills add https://github.com/korwlik23/skills --skill release-version-korwlik23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents inconsistent or error-prone releases by ensuring version bumps, changelog updates, immutable Git tags, and user-facing release notes are produced together and only after validation.

Core Features & Use Cases

  • SemVer-accurate release management: Enforces Semantic Versioning 2.0.0 for deciding MAJOR/MINOR/PATCH and handling pre-releases (alpha/beta/rc).
  • Changelog discipline: Produces human-readable, categorized Keep a Changelog output and updates version references across multiple files.
  • Git tagging and release notes: Creates annotated tags, generates user-facing release notes (highlights, features, fixes, breaking changes, migration guidance), and supports cross-skill integration like updating project sitemaps.

Quick Start

Ask your agent to generate a validated SemVer bump and produce updated changelog and release notes for the next release, including an annotated Git tag.

Frequently Asked Questions about release-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate SemVer version bumps and changelog updates for a new release?

Automating SemVer version bumps and changelog updates requires validating milestone changes or hotfix merges first, then classifying the bump as MAJOR, MINOR, or PATCH. This process synchronizes version references across multiple files and outputs a categorized changelog alongside an annotated Git tag.

What is the difference between a changelog and user-facing release notes?

A changelog provides developer-focused details categorized by Keep a Changelog standards, while user-facing release notes summarize highlights, features, fixes, breaking changes, and migration guidance for end users. Separating these ensures developers get implementation detail while users get actionable summaries.

Can I create immutable Git tags and synchronize version numbers across multiple files?

Yes, creating immutable annotated Git tags and synchronizing version numbers across multiple files is supported. The process enforces strict validation before bumping to prevent inconsistent releases, ensuring all version references and changelog entries are updated together with the tag.

When should I not use automated release versioning for my project?

You should not use automated release versioning if your project bypasses validation steps or requires mutable Git tags. The process strictly enforces immutable tag handling and pre-bump validation, meaning unvalidated milestone changes or hotfix merges cannot proceed through the versioning workflow.