bump-version

Increment plugin and marketplace versions in JSON files using semantic versioning.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/marcospmail/claude-code-plugins --skill bump-version-marcospmail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/marcospmail/claude-code-plugins/tree/main/.claude/skills/bump-version
Command: npx skills add https://github.com/marcospmail/claude-code-plugins --skill bump-version-marcospmail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually updating plugin versions and marketplace metadata can be time-consuming and error-prone. This Skill automates the process, ensuring accurate versioning and efficient release management.

Core Features & Use Cases

  • Automated Version Bumping: Automatically increment version numbers in plugin.json and marketplace.json files.
  • Semantic Versioning: Supports PATCH, MINOR, and MAJOR version increments, adhering to the semantic versioning standard.
  • Version Tracking: Keeps a consistent version history, making it easy to track changes over time.
  • Use Case: When preparing a new release or updating documentation, this Skill can quickly update all relevant version numbers, reducing manual errors and speeding up the process.

Quick Start

Execute the 'bump-version' skill to update the plugin version to the next PATCH level.

Frequently Asked Questions about bump-version

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

FAQPage Schema
How do I automate plugin version updates in marketplace metadata?

Automated version bumping uses semantic versioning to increment plugin and marketplace metadata safely. It supports PATCH, MINOR, and MAJOR increments, ensuring accurate release management by programmatically updating version numbers in your plugin configuration files instead of relying on manual tracking.

How do I increment plugin versions using semantic versioning?

Semantic versioning increments plugin versions by targeting PATCH, MINOR, or MAJOR levels in your configuration files. The skill automatically applies the correct semver increment to both plugin.json and marketplace.json, maintaining a consistent version history for your release management workflow.

What files do I need to update plugin and marketplace release versions?

Updating plugin and marketplace release versions requires access to the plugin.json and marketplace.json files. The skill targets these specific configuration files to apply semantic version increments and keep your release metadata synchronized across your project.

Can I use automated version bumping for both minor and major plugin releases?

Automated version bumping supports PATCH, MINOR, and MAJOR plugin releases. By default, executing the skill updates the plugin to the next PATCH level, but it can handle all semantic versioning increments to accommodate different release management scopes.

Why does manually updating plugin versions cause release management errors?

Manually updating plugin versions causes release management errors because version numbers in plugin.json and marketplace.json can become desynchronized. Automating this process eliminates human error, ensuring accurate versioning and consistent metadata tracking across releases.