bump-version

Increment semantic version components and rewrite plugin.json for a plugin.

Updated Jan 21, 2026

Search Tags:#automation #versioning #CLI #release-management #plugin.json #semantic-versioning #bump

Ready to run

npx skills add https://github.com/powdream/claude-plugins --skill bump-version-powdream

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/powdream/claude-plugins/tree/main/.claude/skills/bump-version
Command: npx skills add https://github.com/powdream/claude-plugins --skill bump-version-powdream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the repetitive task of updating a plugin's version number, ensuring consistent semantic versioning and proper updates to plugin metadata.

Core Features & Use Cases

Automatic version bumping: Increment major, minor, or patch numbers and reset lower components.
Plugin metadata update: Writes the new version to plugins/<plugin-name>/.claude-plugin/plugin.json.
Decision support: If no explicit target is provided, infers from session context and prompts for confirmation before applying changes.
Use Case: When preparing a release, bump the plugin version and ensure the new version is staged for release.

Quick Start

Use the bump-version skill to increment a plugin's version. Example commands:

Bump the version of plugin 'my-plugin' by a minor release.
Bump-version for 'another-plugin' major release.

Frequently Asked Questions about bump-version

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

FAQPage Schema

How do I bump a plugin version in plugin.json automatically?▼

To bump a plugin version automatically, the Skill increments the semantic version component in plugin.json and rewrites the file. It determines the target plugin from a provided name or session context, then applies the chosen major, minor, or patch increment.

What is semantic versioning and how does version bumping handle component resets?▼

Semantic versioning uses major, minor, and patch numbers. When bumping a version, the Skill increments the chosen component and automatically resets all lower-order components to zero to maintain proper versioning format.

Can I update plugin metadata for release management without specifying the plugin name?▼

You can update plugin metadata without specifying a name. The Skill infers the target plugin from the session context and prompts for confirmation before applying the version bump to the plugin.json file.

What is the best way to increment a minor release version for a CLI plugin?▼

The best way to increment a minor release version is to use a bump-version command targeting the specific plugin. It reads the current version, increments the minor number, resets the patch number, and writes the update to plugin.json.

Does the semantic version bumping prompt for confirmation before changing files?▼

Yes, the version bumping process prompts for confirmation. If no explicit target plugin is provided, it infers the plugin from session context and requests confirmation before modifying the plugin.json file.

When do I need to bump a major version instead of a patch during release management?▼

You need to bump a major version when introducing breaking changes, while patch increments are for fixes. The Skill applies the chosen increment and resets lower-order components in the plugin.json file accordingly.