version

Bumps plugin versions in marketplace.json based on git commit history and semver rules.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/kellymears/agents --skill version-kellymears
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version
Source: https://github.com/kellymears/agents/tree/main/.claude/skills/version
Command: npx skills add https://github.com/kellymears/agents --skill version-kellymears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping plugin versions in sync across a marketplace manifest, individual plugin manifests, and documentation is tedious and error-prone. This Skill automates detecting which plugins changed, choosing the correct semver bump, and updating every file consistently. ## Core Features & Use Cases - Change Detection: Compares commits to each plugin's source directory against the last manifest version commit, including uncommitted changes. - Semver Classification: Maps conventional commit prefixes (fix, feat, BREAKING CHANGE) to patch, minor, or major bumps, with user override support. - Dual Manifest Updates: Updates both .claude-plugin/marketplace.json and each plugin's own plugin.json so versions never drift. - Documentation Sync: Reconciles the README plugin table and site homepage plugin list and count with the manifest. - Use Case: After merging several feature commits to the git plugin, ask for a version bump and get a confirmed plan, applied updates, and synced docs in one pass. ## Quick Start Ask the assistant to bump versions for the plugins changed since the last release and confirm the proposed semver plan.

Frequently Asked Questions about version

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

FAQPage Schema
How do I bump plugin versions in a Claude Code marketplace repo?▼

Run the version skill, which detects plugins with commits since the last manifest version change, proposes semver bumps, and updates both marketplace.json and each plugin's plugin.json after your confirmation.

How are semver bump levels determined from git commits?▼

Commits prefixed with fix, style, docs, chore, or perf map to patch; feat maps to minor; BREAKING CHANGE or !: maps to major. The highest level across all commits for a plugin wins.

Can I specify which plugins to bump or force a bump level?▼

Yes. Naming specific plugins skips change detection, and stating a level like "minor bump the git plugin" overrides the commit-based classification. Saying "bump all" bumps every plugin with any changes.

Does the version bump commit changes automatically?▼

No. The skill updates the manifest files and syncs documentation, then reports what changed. Committing is left to the user so they control when version changes land.

What happens if a new plugin is missing from marketplace.json?▼

The skill flags the new plugin instead of bumping it. You must add the plugin entry to marketplace.json first before its version can be managed.