skills.rest
shawn-sandy
shawn-sandyCOMMUNITY
Explore all skills by this author →
Website𝕏@shawnsandyGitHub

release-plugin

Bump a plugin version in plugin.json and align marketplace.json metadata.

Updated Apr 21, 2026
Search Tags:#release management#versioning#git workflow#semver#plugin marketplace#metadata updates
One-click install
npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill release-plugin-shawn-sandy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-plugin
Source: https://github.com/shawn-sandy/agentic-acss-plugins/tree/main/.agents/skills/release-plugin
Command: npx skills add https://github.com/shawn-sandy/agentic-acss-plugins --skill release-plugin-shawn-sandy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The release-plugin skill prevents inconsistent releases by coordinating a plugin.json version bump with the marketplace.json metadata, reducing the chance of mismatched versions or stale descriptions.

Core Features & Use Cases

  • Version bump coordination: Updates the "version" field in plugins/<plugin>/.claude-plugin/plugin.json for the specified plugin.
  • Marketplace metadata consistency: Removes an incorrect "version" key from .claude-plugin/marketplace.json when present, and optionally updates the plugin description.
  • Release-time safety checks: Validates the plugin exists, enforces semver formatting, avoids committing changes, and provides a pre-commit summary.

Quick Start

Run /release-plugin <plugin-name> <new-version> (for example: /release-plugin acss-kit 0.3.1) to validate inputs and generate a clear list of the files that would be modified without committing anything.

Frequently Asked Questions about release-plugin

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

FAQPage Schema
How do I bump a plugin version in plugin.json before a release?▼

To bump a plugin version, you update the "version" field in plugins/<plugin>/.claude-plugin/plugin.json while ensuring the marketplace.json metadata remains consistent and lacks conflicting version keys.

Why does marketplace.json carry a conflicting version field during release prep?▼

A conflicting version field in marketplace.json occurs when manual edits leave a version key behind; release prep requires removing this incorrect key to prevent mismatched releases.

How do I apply semver parsing enforcement for git workflow release versions?▼

Semver parsing enforcement validates that your new version string strictly follows semantic versioning formatting rules before applying any metadata updates to the plugin files.

Can I update the marketplace.json description while bumping the plugin version?▼

Yes, you can optionally update the marketplace.json description during the version bump process to ensure your release metadata is fully consistent and up to date.

Does the release version bump process commit changes to my git workflow automatically?▼

No, the release version bump process does not commit changes automatically; it provides a pre-submit summary of intended file modifications for safe release prep without altering your git state.

Related Skills

Explore More Product & Management Skills→
jcdendritejcdendrite
4

plugin-semver

Validate Semver version bumps in Claude Code plugin.json files.

Community
Intermediate
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
genesis-agentsgenesis-agents
2

Git Automation

Automate Git branching, commits, PRs, and merges across repositories.

Community
Advanced
robbytrobbyt
42

marketplace-bump

Bump plugin versions in marketplace.json using semantic versioning and jq.

Community
Advanced