skills.rest
jcdendrite
jcdendriteCOMMUNITY
Explore all skills by this author →
GitHub

plugin-semver

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

4|1|Updated Mar 11, 2026
Search Tags:#versioning#plugins#semver#release-management#claude-code#pull-request
One-click install
npx skills add https://github.com/jcdendrite/claude-config --skill plugin-semver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-semver
Source: https://github.com/jcdendrite/claude-config/tree/main/plugins/plugin-semver/skills/plugin-semver
Command: npx skills add https://github.com/jcdendrite/claude-config --skill plugin-semver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents breaking or confusing Claude Code plugin updates by ensuring plugin behavior changes are consistently represented with the correct Semver bump.

Core Features & Use Cases

  • Single canonical version source: Keeps version in exactly one place by requiring changes only to the plugin’s .claude-plugin/plugin.json and forbidding adding version to .claude-plugin/marketplace.json.
  • Correct bump magnitude mapping: Forces the bump level to match backward compatibility (patch/minor/major) rather than diff size.
  • Merge-time validation checklist: Prompts authors to emit and verify a required checklist, including a post-merge install command for PR descriptions.

Quick Start

Ask an AI to apply the plugin semver rules to your PR and produce the checklist results, including the post-merge install command.

Frequently Asked Questions about plugin-semver

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

FAQPage Schema
How do I enforce semver versioning for Claude Code plugin changes?▼

You enforce semver versioning for Claude Code plugin changes by validating version bumps against backward compatibility and ensuring the canonical version is updated only in the plugin's `.claude-plugin/plugin.json` file.

When should I bump the major, minor, or patch version for a plugin update?▼

Bump the major, minor, or patch version based on backward compatibility rather than diff size, applying a major bump for breaking changes, minor for new features, and patch for fixes.

Do I need to update the version in marketplace.json for plugin releases?▼

No, you do not need to update the version in `marketplace.json`. The skill enforces a single canonical version source by forbidding version keys in `marketplace.json` and requiring changes only in `plugin.json`.

How do I generate a pull request checklist for a plugin version bump?▼

You generate a pull request checklist for a plugin version bump by asking an AI to apply the semver rules to your PR, which produces a required validation checklist including the exact post-merge install command.

Related Skills

Explore More Software Engineering Skills→
robbytrobbyt
42

plugin-bump

Bump plugin.json versions using jq with semantic versioning rules.

Community
Intermediate
coco-researchcoco-research
264

gsd-ship

Push a verified branch and create a merge-ready pull request.

Community
Advanced
GitnappGitnapp

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced
shawn-sandyshawn-sandy

release-plugin

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

Community
Intermediate