Version Bumper FAQs

Question 1

What validation checks does the Version Bumper perform?

Accepted Answer

The skill performs several safety checks, including verifying that the version follows SemVer formatting, ensuring the new version is higher than the current one, checking for duplicate versions in the repository, and validating that all synchronized files match.

Question 2

How does this skill improve my plugin development workflow?

Accepted Answer

It eliminates manual errors by ensuring version consistency across plugin.json, marketplace.extended.json, and the final marketplace.json. By automating CHANGELOG updates and Git commands, it reduces the time spent on administrative release tasks, allowing you to focus on coding.

Question 3

When should I use the different bump types (Major, Minor, Patch)?

Accepted Answer

Use a Patch bump for backward-compatible bug fixes; a Minor bump for adding new features that remain backward compatible; and a Major bump for breaking changes or significant API overhauls that are not backward compatible.

Question 4

What does the Version Bumper Claude Code skill do?

Accepted Answer

The Version Bumper skill automates the semantic versioning (SemVer) process for Claude Code plugins. It calculates version increments (major, minor, or patch), updates version strings across multiple manifest files, synchronizes marketplace catalogs, and handles Git release tagging.

Question 5

Does Version Bumper integrate with Git and GitHub?

Accepted Answer

Yes. The skill features deep Git integration, capable of staging modified manifest files, creating standardized 'chore' commits, and generating annotated release tags (e.g., v1.0.0) that are ready to be pushed to your repository.

Version Bumper

Version Bumper

Key Features

Use Cases

Key Features

Use Cases