LaunchKit · 2026
Back to Skills

semver-helper

Semantic Versioning 2.0.0 reference guide.

0
372 downloads
by @avegancafe

Setup & Installation

openclaw skills install @avegancafe/semver-helper

Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:

npx clawhub install semver-helper

Version History

v1.0.1Feb 18, 2026 - Version note by skill developer:

Simplify to static reference guide

What This Skill Does

Reference guide for Semantic Versioning 2.0.0 decisions. Covers when to increment MAJOR, MINOR, or PATCH, with a decision tree, real examples, pre-release naming, and common edge cases.

Cuts through the full semver spec with a decision tree and concrete examples, so you get an answer in seconds instead of reading documentation.

When to use it

  • Deciding whether removing a deprecated API endpoint requires a MAJOR bump
  • Checking which number to increment before publishing an npm package
  • Resolving the correct bump when a PR contains both a bug fix and a new feature
  • Picking the right pre-release label (alpha, beta, rc) before a stable release
  • Confirming whether an internal refactor that preserves behavior needs a version change

Example Workflow

Here's how your AI assistant might use this skill in practice.

INPUT

User asks: I renamed a public function from removeUser() to deleteUser() — what version should I bump to?

AGENT
  1. 1Check whether the change affects something users depend on
  2. 2Identify the rename as a breaking change, since users must update all call sites
  3. 3Apply the MAJOR bump rule: breaking changes increment the first number
  4. 4Note that MINOR and PATCH reset to 0 after a MAJOR bump
OUTPUT

Bump to the next MAJOR version (e.g. 1.2.3 → 2.0.0), since renaming a public function is a breaking API change.