home / skills / jeremylongshore / claude-code-plugins-plus-skills / version-bumper

This skill automates semantic version bumps across plugin.json and marketplace catalogs, ensuring consistency and traceable updates in the repository.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill version-bumper

Review the files below or copy the command above to add this skill to your agents.

Files (9)
SKILL.md
1.4 KB
---
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: 1.0.0
author: Jeremy Longshore <[email protected]>
license: MIT
---

# Version Bumper

## Overview

This skill provides automated assistance for the described functionality.

## Prerequisites

- Appropriate file access permissions
- Required dependencies installed

## Instructions

1. Invoke this skill when the trigger conditions are met
2. Provide necessary context and parameters
3. Review the generated output
4. Apply modifications as needed

## Output

The output is a concrete, repo-ready version bump plan and execution summary, including the computed `old_version → new_version`, the exact files updated (plugin `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.extended.json`, regenerated `.claude-plugin/marketplace.json` when applicable), and the next validation commands to run.

## Error Handling

See `{baseDir}/references/errors.md` for comprehensive error handling.

## Examples

See `{baseDir}/references/examples.md` for detailed examples.

## Resources

- Project documentation
- Related skills and commands

Overview

This skill automates semantic version updates across plugin.json and marketplace catalog files when a version bump, update, or release is requested. It ensures consistent versioning across the AI assistant-code-plugins repository and generates a clear, repo-ready plan. Use it to minimize manual edits and prevent mismatched versions in plugin manifests and marketplace entries.

How this skill works

When triggered by a phrase like “bump version”, “update version”, or “release”, the skill scans the repository for plugin manifests and marketplace files. It computes the new semantic version based on input or inferred bump type, updates plugin .claude-plugin/plugin.json and marketplace.extended.json, and regenerates marketplace.json when applicable. The skill returns a summary showing old_version → new_version, exact files changed, and suggested validation commands.

When to use it

  • You plan a release and need a coordinated version bump across plugins and marketplace files.
  • A reviewer or CI job flags inconsistent versions between plugin.json and marketplace entries.
  • You want to automate routine patch/minor/major bumps across many plugin packages.
  • Before running validation or publishing steps to ensure manifests match the intended release.

Best practices

  • Provide explicit bump type (patch/minor/major) or exact new version to avoid ambiguity.
  • Run the skill in a branch or draft PR to review changes before merge.
  • Verify file access and repository permissions before execution to prevent partial updates.
  • Run the suggested validation commands after the bump to confirm manifest integrity and marketplace compatibility.
  • Keep changelogs or release notes updated alongside the version bump for traceability.

Example use cases

  • Developer says “bump version to 1.4.2” and receives a plan plus updated plugin.json and marketplace files ready for commit.
  • CI detects a release tag and invokes the skill to propagate the new semantic version across all affected manifests.
  • A maintainer requests a minor bump across multiple plugins; the skill updates each plugin’s plugin.json and regenerates marketplace.json where required.
  • Pre-release checklist: run the skill, review the summary, execute validation commands, then open a PR with the automated changes.

FAQ

Can I specify an exact new version or just a bump type?

You can provide either an exact version or a bump type (patch/minor/major). If only a type is given, the skill computes the next semantic version automatically.

Which files are updated by the skill?

It updates plugin .claude-plugin/plugin.json and .claude-plugin/marketplace.extended.json, and regenerates .claude-plugin/marketplace.json when applicable. The summary lists every file changed.