skills.rest
osolmaz
osolmazCOMMUNITY
Explore all skills by this author →
Website𝕏@onusozGitHub

semver

Determine the next release version by applying SemVer rules to public API changes.

12|2|Updated Jan 2, 2026
Search Tags:#versioning#semver#release-management#api-compatibility#software-release#bump-decision
One-click install
npx skills add https://github.com/osolmaz/tools --skill semver-osolmaz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: semver
Source: https://github.com/osolmaz/tools/tree/main/agents/skills/semver
Command: npx skills add https://github.com/osolmaz/tools --skill semver-osolmaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Determine next release version by assessing public API compatibility and release policy to decide the appropriate bump.

Core Features & Use Cases

  • Determine major, minor, or patch increments based on API changes and compatibility promises.
  • Apply 0.y.z rules for pre-1.0 projects, including stability cautions and deprecation guidance.
  • Use a release policy and changelog references to justify each bump in automated pipelines.

Quick Start

Tell the tool to compute the next version bump by analyzing the pending changes against the public API surface and the project's release policy.

Frequently Asked Questions about semver

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

FAQPage Schema
How do I determine the next release version for my software based on API changes?▼

Pre-1.0 projects follow special 0.y.z rules under SemVer, where minor versions indicate potential instability. Apply stability cautions and deprecation guidance to evaluate API compatibility and decide the appropriate bump for early releases.

How do I automate release management and bump decisions in CI pipelines?▼

Automate release management by computing version bumps from changelog references and pending changes against the public API surface. Use the resulting bump decision in automated pipelines to enforce versioning consistency.

When should I bump the major version of a library or CLI?▼

Bump the major version when changes break public API compatibility promises. Evaluate pending changes and tests against the public API surface to determine if a major increment is required by the release policy.

Does this work for both libraries and CLIs with clear public APIs?▼

Yes, it applies to libraries and CLIs with clear public APIs. The tool evaluates API compatibility, deprecation considerations, and release policy to enforce the correct version bump across major, minor, and patch decisions.

What are the limitations of using SemVer rules for pre-1.0 stability?▼

SemVer pre-1.0 rules carry inherent stability cautions, meaning public APIs may change without triggering a major bump. You should not rely on strict compatibility guarantees during 0.y.z development phases.

Related Skills

Explore More Software Engineering Skills→
prettysmartdevprettysmartdev
64

release-prep

Update version numbers, docs, and blog content for release preparation.

Official
Intermediate
no-problem-devno-problem-dev
5

changelog-manage

Add categorized entries to CHANGELOG.md and calculate semantic version bumps.

Official
Intermediate
PlagueHOPlagueHO
4

release-changelog

Update CHANGELOG.md and create a release tag from commits since the last version tag.

Community
Advanced
ruifrvazruifrvaz
3

smaqit.release-approval

Validate release version approval via pattern matching or user confirmation.

Community
Intermediate