bump-version

Name: bump-version
Availability: InStock
Author: vzco

Update and verify version numbers across plugin and marketplace config files.

15|4|Updated Mar 7, 2026

Search Tags:#automation #plugin #release #config #marketplace #bump #version

Ready to run

npx skills add https://github.com/vzco/arc-probe --skill bump-version-vzco

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Version drift across plugin and marketplace configuration files is common during releases. This skill automates updating the version string in all relevant files to ensure consistency and reduce manual errors.

Core Features & Use Cases

Batch version updates: updates the version field in plugin/.claude-plugin/plugin.json, public-repo/.claude-plugin/marketplace.json, and public-repo/plugins/arc-probe/.claude-plugin/plugin.json to the new version.
Release-safe verification: ensures all three files reflect the same version and reports any mismatch without committing.
Non-destructive workflow: designed to be used as part of a release pipeline, with a clear, auditable update trace.

Quick Start

Provide the new_version string to update all three files and verify their versions are identical.

Frequently Asked Questions about bump-version

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

FAQPage Schema

How do I sync version numbers across multiple plugin config files during a release?▼

To sync version numbers across plugin config files, provide a new version string to update and verify the version field in plugin.json and marketplace.json files. This ensures all configurations reflect the identical version without requiring manual edits.

What's the best way to automate version bumps for marketplace.json and plugin.json files?▼

Automating version bumps for marketplace.json and plugin.json files involves reading the target configurations, replacing the old version string with the new value, and verifying consistency. This non-destructive process updates three specific files without committing changes.

Why does version drift happen in plugin release workflows and how can I prevent it?▼

Version drift in plugin release workflows happens when configuration files are updated manually at different times. Prevent drift by batch updating the version string across plugin.json and marketplace.json files simultaneously, ensuring all files match before committing.

Does the version update process commit changes directly to the repository?▼

No, the version update process does not commit changes directly to the repository. It operates as a non-destructive workflow that reads three target files, applies the new version, verifies they match, and leaves the changes uncommitted for audit purposes.

Can I verify version consistency across plugin directories before finalizing a release?▼

Yes, you can verify version consistency across plugin directories before finalizing a release. The process checks that all three target config files, including the arc-probe plugin.json, report any mismatches, ensuring a unified version without committing.

What files do I need to update when bumping a version in a plugin directory?▼

When bumping a version in a plugin directory, you need to update the version field in plugin/.claude-plugin/plugin.json, public-repo/.claude-plugin/marketplace.json, and public-repo/plugins/arc-proe/.claude-plugin/plugin.json to maintain configuration consistency.