Skip to content
Skills Library
Programming · Automation

version-bumper

/version-bumper

Execute automatically handles semantic version updates across plugin.json and marketplace catalog when user mentions version bump, update version, or release. ensures version consistency in AI assistant-code-plugins repository. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
11
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Execute automatically handles semantic version updates across plugin.json and marketplace catalog when user mentions version bump, update version, or release. ensures version consistency in AI assistant-code-plugins repository. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

Original author description

Execute automatically handles semantic version updates across plugin.json and marketplace catalog when user mentions version bump, update version, or release. ensures version consistency in AI assistant-code-plugins repository. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

How it works

  1. Overview
  2. Prerequisites
  3. Instructions
  4. Output
  5. Error Handling
  6. Examples
  7. Resources
Original SKILL.md headings · 65 lines, 499 words
SKILL.md preview
---
name: version-bumper
description: 'Execute automatically handles semantic version updates across plugin.json
  and marketplace catalog when user mentions version bump, update version, or release.
  ensures version consistency in AI assistant-code-plugins repository. Use when appropriate
  context detected. Trigger with relevant phrases based on skill purpose.

  '
allowed-tools: Read, Write, Edit, Grep, Bash(cmd:*)
version: 2.21.0
author: Jeremy Longshore <jeremy@intentsolutions.io>
license: MIT
tags:
- example
- version-bumper
compatibility: Designed for Claude Code
---
# Version Bumper

## Overview

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.

## Prerequisites

- `jq` installed and available on PATH for JSON manipulation
- Read/write access to `.claude-plugin/plugin.json` and `.claude-plugin/marketplace.extended.json`
- `pnpm run sync-marketplace` available at the repository root
- Git installed for optional tag creation

## Instructions

1. Identify the target plugin directory and read the current version from `.claude-plugin/plugin.json` using `jq -r '.version'`.
2. Determine the bump type (major, minor, or patch) from the user request. If unspecified, infer from the nature of changes: breaking changes warrant major, new features warrant minor, and fixes warrant patch.
3. Parse the current version into its `major.minor.patch` components and compute the new version according to semver rules (see [`references/version-bump-process.md`](references/version-bump-process.md)).
4. Update the `"version"` field in `.claude-plugin/plugin.json` with the new version string.
5. Locate the plugin entry in `.claude-plugin/marketplace.extended.json` and update its `"version"` field to match (see [`references/update-locations.md`](references/update-locations.md)).
6. Run `pnpm run sync-marketplace` at the repository root to regenerate `marketplace.json`.
7. Verify version consistency across all three files by reading each and confirming the version strings match.
8. Optionally create a git tag (`git tag -a "v<new_version>" -m "Release v<new_version>"`) and prepare a commit message following the `chore: Release v<version>` convention (see [`references/release-workflow.md`](references/release-workflow.md)).

## Output

A version bump execution summary containing:

- The computed transition (`old_version` to `new_version`)
- The exact files updated: `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.extended.json`, and regenerated `.claude-plugin/marketplace.json`
- Validation confirmation that all files carry the same version
- Suggested next commands (`git add`, `git commit`, `git tag`, validation scripts)

## Error Handling

| 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 |

## Examples

**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.

## Resources

- [`references/version-bump-process.md`](references/version-bump-process.md) -- step-by-step bump algorithm
- [`references/update-locations.md`](references/update-locations.md) -- all files requiring version updates
- [`references/release-workflow.md`](references/release-workflow.md) -- full release process including git tags
- [`references/examples.md`](references/examples.md) -- additional usage scenarios
- [Semantic Versioning specification](https://semver.org/)
Files in this package (11)
  • SKILL.md 5 KB
  • assets/README.md 1 KB
  • references/ARD.md 4 KB
  • references/PRD.md 3 KB
  • references/README.md 1 KB
  • references/errors.md 1 KB
  • references/examples.md 1 KB
  • references/release-workflow.md 1 KB
  • references/update-locations.md 1 KB
  • references/version-bump-process.md 1 KB
  • scripts/README.md 1 KB

Versions

RepositoryScoreLicence
This page · jeremylongshore/tons-of-skills-marketplace100MIT
jeremylongshore/tons-of-skills-marketplace100MIT

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version f91952f4330a (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100version
    This skill should be used when the user wants to bump versions, create releases, or tag versions. Triggers include: "bump version", "bump the version", "version bump", "release version", "tag a release", "create release", "major/minor/patch bump", "update version", "new…
  • 100version-bump
    Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the…
  • 90marketplace
    Use when working on the cc-plugins repository itself: adding a plugin, renaming one, removing one, bumping a version, or after editing any plugin's components. Also when writing or revising a skill's description or body, or editing CLAUDE.md — WRITING.md carries the judgment for…
  • 100plugin-version
    Bump plugin versions in the OpenSaaS Stack monorepo. Invoke whenever any file under claude-plugins/* or .claude-plugin/ is modified — skills, commands, agents, or marketplace config. Plugin versions must be bumped before committing so users who install the plugin get the updated…
  • 100plugin-version
    Bump plugin versions in the OpenSaaS Stack monorepo. Invoke whenever any file under Codex-plugins/* or .Codex-plugin/ is modified — skills, commands, agents, or marketplace config. Plugin versions must be bumped before committing so users who install the plugin get the updated…
  • 100version-bump
    ACTIVATE before every `gh pr create` / `gh pr edit` in the claude-marketplace repo, and before any commit that touches files under plugins/. ACTIVATE for 'bump version', 'bump les versions', 'release plugin', 'version bump', 'semver', 'mets à jour les versions'. Classifies the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.