Semantic Version Advisor

Classify semantic version changes and recommend MAJOR, MINOR, or PATCH bumps.

1|Updated Sep 9, 2025
One-click install
npx skills add https://github.com/alienfast/claude --skill semantic-version-advisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Semantic Version Advisor
Source: https://github.com/alienfast/claude/tree/main/skills/semver-advisor
Command: npx skills add https://github.com/alienfast/claude --skill semantic-version-advisor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, semver, and includes resources (resource) components.

What problem does it solve?

Incorrectly applying semantic versioning (SemVer) can lead to broken builds, unexpected compatibility issues, and confusion among developers. This Skill eliminates the guesswork from versioning, providing clear, accurate advice on how to classify changes and determine the correct MAJOR, MINOR, or PATCH bump for your releases and dependencies.

Core Features & Use Cases

  • Version Change Classification: Automatically determines if a version update is MAJOR, MINOR, or PATCH based on SemVer rules, with clear explanations.
  • Version Bump Recommendation: Advises on the appropriate version increment (MAJOR, MINOR, PATCH) based on a list of changes, ensuring consistency.
  • Version Proposal Validation: Checks if a proposed version bump is valid according to SemVer rules, including segment resets and change severity matching.
  • Use Case: Before releasing a new library version, provide a list of changes (e.g., "fixed bug X, added feature Y, removed API Z"). The Skill will tell you if it should be a MAJOR, MINOR, or PATCH release and why.

Quick Start

Classify the version change from 1.2.3 to 2.0.0. Explain why.

Frequently Asked Questions about Semantic Version Advisor

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

FAQPage Schema
How do I determine if a version change should be MAJOR, MINOR, or PATCH?

Semantic versioning classifies changes by impact: MAJOR for breaking changes, MINOR for backward-compatible features, PATCH for bug fixes. This Skill analyzes your changes and recommends the correct bump with clear reasoning based on SemVer rules.

When should I bump the MAJOR version versus MINOR or PATCH?

Bump MAJOR when you introduce breaking changes that affect backward compatibility. MINOR adds functionality without breaking existing code. PATCH fixes bugs without new features. This Skill evaluates your changes to determine which applies.

How do I validate that my proposed version bump follows semantic versioning rules?

Semantic versioning enforces strict rules: MAJOR.MINOR.PATCH increments, segment resets when higher precedence changes, and pre-release handling. This Skill validates your proposed bump against these rules and explains whether it's correct.

Can I use semantic versioning for dependency updates and release planning?

Yes. This Skill classifies version changes for both dependency upgrades and release planning, analyzing compatibility impact and drift to help you choose appropriate version increments across your projects.

What if my version includes pre-releases or range prefixes—does semantic versioning still apply?

Semantic versioning handles pre-releases and range prefixes like caret or tilde operators. This Skill parses these formats, ignores irrelevant prefixes, and applies SemVer rules to determine the correct classification and bump.

How do I decide between a version bump and a compatibility assessment for migration impact?

Before migrating or upgrading, assess compatibility impact by analyzing the version change. This Skill classifies the change severity and explains whether your code risks breaking, helping you plan migrations safely.