skills.rest
rayshan
rayshanCOMMUNITY
Explore all skills by this author →
Website𝕏@rayshanGitHub

bump-plugin-version

Bumps the version field in a plugin.json manifest using semantic versioning.

Updated Aug 23, 2026
Search Tags:#automation#versioning#plugins#plugin.json#semantic-versioning#bump#code-management
One-click install
npx skills add https://github.com/rayshan/agent-plugins --skill bump-plugin-version
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bump-plugin-version
Source: https://github.com/rayshan/agent-plugins/tree/main/ray-agent-plugins/skills/bump-plugin-version
Command: npx skills add https://github.com/rayshan/agent-plugins --skill bump-plugin-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers maintain consistent release versions by automatically updating the plugin.json version field according to semantic versioning rules.

Core Features & Use Cases

  • Controlled version bumps: bump patch, minor, or major versions, or use an exact version, with validation.
  • Manifest integrity: updates only the version field in plugin.json, preserving other fields.
  • Release automation: ideal for CI pipelines or developer workflows updating plugins across environments.

Quick Start

Provide the plugin name and desired version bump or exact version, then run the skill to update the version in its plugin.json.

Frequently Asked Questions about bump-plugin-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?▼

To bump a plugin version in plugin.json, the Skill reads the manifest, computes the new semantic version based on your specified bump type, validates the SemVer format, and updates the version field using an Edit operation.

Can I set an exact version number instead of bumping?▼

Yes, you can set an exact version number. The Skill supports patch, minor, and major version bumps, but also allows you to specify an exact version string, which it validates against semantic versioning rules before updating.

Does updating the plugin manifest preserve other fields?▼

Updating the plugin manifest preserves other fields. The Skill targets only the version field in plugin.json, ensuring manifest integrity while applying the new semantic version for your release.

What is the best way to automate plugin versioning for releases?▼

The best way to automate plugin versioning is using a Skill that enforces semantic versioning. It calculates the correct version bump, validates the format, and updates plugin.json, making it ideal for CI pipelines or developer workflows.

When do I need semantic versioning for plugin deployments?▼

You need semantic versioning for plugin deployments when releasing updates across a workspace or marketplace. It enforces consistent release versions by automatically updating the plugin.json version field according to SemVer rules.

Related Skills

Explore More Software Engineering Skills→
pabloimrik17pabloimrik17

plugin-version-bump

Update plugin.json and marketplace entries to consistent version strings.

Community
Intermediate
emdashcodesemdashcodes
13

claude-code-plugins

Plan, package, and distribute Claude Code plugins and marketplaces.

Community
Intermediate
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced
dhofheinzdhofheinz
9

Plugin Metadata Skill

Validate, update, and generate Claude Code plugin metadata with semantic versioning checks.

Community
Basic