skills.rest
wizact
wizactCOMMUNITY
Explore all skills by this author →
Website𝕏@amirmohtasebiGitHub

bump-plugin-version

Analyze git changes to apply semantic version bumps to plugin.json and marketplace.json.

1|Updated Oct 18, 2025
Search Tags:#automation#git#release management#versioning#semantic versioning#plugin management
One-click install
npx skills add https://github.com/wizact/dotclaude --skill bump-plugin-version-wizact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bump-plugin-version
Source: https://github.com/wizact/dotclaude/tree/main/wizact-marketplace/plugins/wizact-utilities/skills/bump-plugin-version
Command: npx skills add https://github.com/wizact/dotclaude --skill bump-plugin-version-wizact

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious process of updating version numbers across multiple configuration files after making changes to a plugin, ensuring semantic versioning compliance.

Core Features & Use Cases

  • Semantic Versioning: Automatically determines MAJOR, MINOR, or PATCH bumps based on git changes.
  • Multi-file Updates: Updates both plugin.json and marketplace.json for consistent versioning.
  • Use Case: After adding a new feature to a plugin, run this Skill to automatically update its version, the marketplace entry, and the overall marketplace version, preparing it for release.

Quick Start

Run the bump-plugin-version skill to automatically update versions for the current plugin.

Frequently Asked Questions about bump-plugin-version

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

FAQPage Schema
How do I automate semantic version bumps for plugin configuration files?▼

You can automate semantic version bumps by analyzing git changes to determine MAJOR, MINOR, or PATCH updates, then applying them directly to your plugin configuration files. This ensures consistent versioning and prepares your plugin for release.

How does git change analysis determine semantic versioning updates for plugins?▼

Git change analysis determines semantic versioning updates by evaluating commit history to decide whether a MAJOR, MINOR, or PATCH bump is required. It then applies this calculated version to both individual plugin and marketplace manifest files.

Do I need git command-line interface to automate plugin version updates?▼

Yes, you need the git command-line interface installed and accessible. The semantic versioning automation relies on git to analyze repository changes and requires JSON file manipulation capabilities to update the configuration manifests.

Can I update both plugin.json and marketplace.json versions at the same time?▼

Yes, multi-file updates are supported. The automation simultaneously updates both the plugin.json and marketplace.json files, ensuring versioning consistency across individual plugin configurations and the overarching marketplace manifest.

What is the best way to manage release versions for multiple plugins in a marketplace?▼

The best way to manage marketplace release versions is automating the update process across multiple configuration files. This approach calculates semantic version bumps from git changes and applies them consistently to both plugin and marketplace manifests.

Related Skills

Explore More Software Engineering Skills→
bismuthdigitalbismuthdigital

version

Analyzes code changes to update semantic version files and create Git tags.

Official
Advanced
tianzecntianzecn
2

release

Automate version bumps, marketplace.json updates, git tagging, and release documentation for MAG Claude Plugins.

Community
Advanced
DrLuggelsDrLuggels
3

changelog-automation

Generate changelogs and release notes from Conventional Commits.

Community
Advanced
bbrowningbbrowning
2

Creating and Managing Plugin Marketplaces

Create Claude Plugin marketplaces with manifest files and git workflows.

Community
Basic