Does this skill support pre-release versions?

Yes, it provides specific guidance and protocols for using -alpha, -beta, and -rc tags to handle unstable development phases without bumping production versions.

What is EffVer in the context of this skill?

EffVer, or Effort-based Versioning, is an alternative to SemVer that categorizes updates by the migration effort required (Macro, Meso, Micro) rather than strictly by API breaking changes.

Which files can this skill synchronize?

The skill can synchronize version numbers across package.json, plugin.json, marketplace.json, VERSION.md, and any project-specific targets defined in your configuration.

How does the skill prevent version inflation?

It encourages staying on 0.x.y versions for pre-production projects and batching breaking changes together to avoid jumping major versions during rapid AI refactoring.

Smart Version Management

Name: Smart Version Management
Author: murillodutt

bymurillodutt

0•

Developer Tools

Manages project versioning strategy and multi-file synchronization using Semantic and Effort-based versioning frameworks.

The Versioning skill for Claude Code provides a rigorous framework for software release management, specifically optimized for the rapid development cycles of AI-driven projects. It implements a structured decision tree to help developers choose between Semantic Versioning (SemVer) and Effort-based Versioning (EffVer), preventing the common issue of 'version inflation' during early-stage development. By enforcing a 'one version, one reality' sync protocol, it ensures that version numbers remain consistent across package.json, documentation, and metadata files automatically.

Key Features

01Standardized pre-release tagging for alpha, beta, and release candidates

02Automated version synchronization across multiple project artifacts

03SemVer vs. EffVer decision logic for production and pre-production

04Centralized source-of-truth management via VERSION files

050 GitHub stars

06Anti-inflation strategies for high-frequency AI development cycles

Use Cases

01Deciding whether a set of changes requires a MAJOR, MINOR, or PATCH bump

02Synchronizing version numbers across package.json, VERSION.md, and marketplace manifests

03Maintaining stable 0.x.y versioning for internal tools until API stability is reached

Key Features

01Standardized pre-release tagging for alpha, beta, and release candidates

02Automated version synchronization across multiple project artifacts

03SemVer vs. EffVer decision logic for production and pre-production

04Centralized source-of-truth management via VERSION files

050 GitHub stars

06Anti-inflation strategies for high-frequency AI development cycles

Use Cases

01Deciding whether a set of changes requires a MAJOR, MINOR, or PATCH bump

02Synchronizing version numbers across package.json, VERSION.md, and marketplace manifests

03Maintaining stable 0.x.y versioning for internal tools until API stability is reached