version-bump

Detect changed plugins from git diffs and update version fields in plugin.json and marketplace.json.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill version-bump-mattbobambrose
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/mattbobambrose/mattbobambrose-claude-skills/tree/main/plugins/project-tools/skills/version-bump
Command: npx skills add https://github.com/mattbobambrose/mattbobambrose-claude-skills --skill version-bump-mattbobambrose

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious and error-prone task of finding which plugins changed and ensuring their version numbers are consistently updated across plugin.json and marketplace.json, preventing release mismatches and manual mistakes.

Core Features & Use Cases

  • Detects changed plugin directories by inspecting git diffs and staged changes.
  • Determines semantic version bump level (patch, minor, major) based on the nature of changes and guidance.
  • Updates the "version" field inside plugins/*/.claude-plugin/plugin.json and the corresponding entry in .claude-plugin/marketplace.json, warning if a plugin is missing from the marketplace and never committing changes.
  • Use case: run before publishing or preparing a release to ensure plugin and marketplace versions stay synchronized.

Quick Start

Run the version-bump skill to detect modified plugins, choose bump levels, and update plugin.json and marketplace.json versions without committing any changes.

Frequently Asked Questions about version-bump

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

FAQPage Schema
How do I automatically bump plugin versions in a marketplace based on git diffs?

To bump plugin versions automatically, this Skill reads git diffs to detect changed plugin directories and updates semantic version fields in both plugin.json and marketplace.json. It increments versions consistently without committing changes.

How does semantic version detection work for plugin releases?

Semantic version detection works by inspecting git diffs and staged changes to identify modified plugins, then determining the bump level (patch, minor, or major) based on the nature of the changes and provided guidance.

Do I need a specific repository structure to automate plugin versioning?

Yes, automating plugin versioning requires a specific repository structure organized with plugins/<name> directories and a .claude-plugin/marketplace.json file to properly map and update version fields.

What happens if a changed plugin is missing from marketplace.json during a version bump?

If a changed plugin is missing from marketplace.json, the version bump process issues a warning instead of failing. It updates the plugin.json version field while alerting you to the missing marketplace entry.

What's the best way to keep plugin.json and marketplace.json versions synchronized before a release?

The best way to keep versions synchronized is running an automated version bump before publishing. This detects modified plugins via git diffs and updates both plugin.json and marketplace.json version fields simultaneously.