semver

Validate and enforce SemVer 2.0.0 version bumps and formatting for releases.

1|Updated Mar 7, 2026

Search Tags:#versioning #deprecation #semver #release-management #pre-release #api-versioning #build-metadata

Ready to run

npx skills add https://github.com/kayaman/skills --skill semver-kayaman

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: semver
Source: https://github.com/kayaman/skills/tree/main/skills/semver
Command: npx skills add https://github.com/kayaman/skills --skill semver-kayaman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent application of Semantic Versioning 2.0.0 across releases, guiding correct version bumps and reducing release risk.

Core Features & Use Cases

Enforces the SemVer 2.0.0 version format MAJOR.MINOR.PATCH with optional pre-release and build metadata.
Validates and suggests appropriate bump levels (MAJOR for breaking changes, MINOR for new features, PATCH for bug fixes) and supports deprecation workflows.
Supports tagging, comparison, and policy enforcement for release pipelines across multiple packages and platforms.

Quick Start

Validate the current version and determine the next appropriate bump for a release.

Frequently Asked Questions about semver

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

FAQPage Schema

How do I know if I need a MAJOR, MINOR, or PATCH version bump for my software release?▼

Semantic versioning requires a MAJOR bump for breaking changes, a MINOR bump for new backward-compatible features, and a PATCH bump for backward-compatible bug fixes. Enforcing these SemVer 2.0.0 rules reduces release risk and ensures dependency stability.

What is the correct format for pre-release versions and build metadata in semantic versioning?▼

Semantic versioning format follows MAJOR.MINOR.PATCH with optional pre-release identifiers and build metadata appended as hyphen-separated segments. This extended SemVer 2.0.0 syntax allows accurate tagging of release candidates and custom build artifacts.

How do I enforce semantic versioning compliance across multiple packages in a release pipeline?▼

You can enforce semantic versioning compliance across multiple packages by validating version formats and applying bump policies within your release pipeline. This ensures consistent API versioning and automated deprecation workflows across different platforms.

When do I need to use semantic versioning for public API management?▼

You need semantic versioning for public API management when releasing updates that introduce new features, fix bugs, or break existing contracts. It clearly signals API versioning changes and manages deprecation workflows to prevent dependency conflicts.

What is the best way to handle deprecation workflows when bumping a MAJOR semantic version?▼

Handling deprecation workflows during a MAJOR semantic version bump requires clearly tagging removed functionality and communicating breaking changes. This enforces SemVer 2.0.0 compliance while guiding users through dependency management transitions.