Help us improve
Share bugs, ideas, or general feedback.
From jeremy-plugin-tool
Automates semantic version bumps across plugin.json, marketplace.extended.json, and marketplace.json in Claude Code plugins. Triggers on mentions of version bump, update version, or release for consistency.
npx claudepluginhub jeremylongshore/claude-code-plugins-plus-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/jeremy-plugin-tool:version-bumperThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automates semantic version bumps across all version-bearing files in a Claude Code plugin. Ensures consistency between `plugin.json`, `marketplace.extended.json`, and the generated `marketplace.json` catalog.
Bumps semantic versions (major/minor/patch) for Claude Code plugins, updates plugin.json and marketplace.json, creates git commit and tag. Use after features, bug fixes, or breaking changes.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Automates semantic version bumps across all version-bearing files in a Claude Code plugin. Ensures consistency between plugin.json, marketplace.extended.json, and the generated marketplace.json catalog.
jq installed and available on PATH for JSON manipulation.claude-plugin/plugin.json and .claude-plugin/marketplace.extended.jsonpnpm run sync-marketplace available at the repository root.claude-plugin/plugin.json using jq -r '.version'.major.minor.patch components and compute the new version according to semver rules (see ${CLAUDE_SKILL_DIR}/references/version-bump-process.md)."version" field in .claude-plugin/plugin.json with the new version string..claude-plugin/marketplace.extended.json and update its "version" field to match (see ${CLAUDE_SKILL_DIR}/references/update-locations.md).pnpm run sync-marketplace at the repository root to regenerate marketplace.json.git tag -a "v<new_version>" -m "Release v<new_version>") and prepare a commit message following the chore: Release v<version> convention (see ${CLAUDE_SKILL_DIR}/references/release-workflow.md).A version bump execution summary containing:
old_version to new_version).claude-plugin/plugin.json, .claude-plugin/marketplace.extended.json, and regenerated .claude-plugin/marketplace.jsongit add, git commit, git tag, validation scripts)| Error | Cause | Solution |
|---|---|---|
jq: command not found | jq not installed | Install via apt install jq or brew install jq |
| Version format invalid | Non-semver string in plugin.json | Correct to x.y.z format before bumping |
| Plugin not found in marketplace | Missing catalog entry | Add the plugin to marketplace.extended.json first |
| Sync marketplace failure | Schema mismatch or missing fields | Run jq empty on both JSON files to locate syntax errors |
| Version mismatch after sync | sync-marketplace did not pick up changes | Verify the plugin name in marketplace.extended.json matches plugin.json exactly |
Patch bump for a specific plugin:
Trigger: "Bump the security-scanner plugin to patch version"
Process: Read current version 1.2.3, compute 1.2.4, update plugin.json and marketplace.extended.json, run sync, verify consistency, report success.
Explicit major release:
Trigger: "Release version 2.0.0 of plugin-name"
Process: Set version to 2.0.0 in all files, sync marketplace, create git tag v2.0.0, prepare commit with chore: Release v2.0.0.
Feature-based minor bump: Trigger: "Increment version for new feature" Process: Detect minor bump, compute 1.2.3 to 1.3.0, update all version locations, sync, validate, report completion.
${CLAUDE_SKILL_DIR}/references/version-bump-process.md -- step-by-step bump algorithm${CLAUDE_SKILL_DIR}/references/update-locations.md -- all files requiring version updates${CLAUDE_SKILL_DIR}/references/release-workflow.md -- full release process including git tags${CLAUDE_SKILL_DIR}/references/examples.md -- additional usage scenarios