mcpbeat

Bump Plugin Version

vinta/bump-plugin-version

(project) Use when editing any file under skills/hal-skills/ or plugins/hal-voice/ to bump the plugin version before committing

313 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
123
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/vinta/hal-9000 --skill bump-plugin-version

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

2 sections, as written by the author

Bump Plugin Version

After editing files under skills/hal-skills/ or plugins/hal-voice/, bump the plugin's version field in .claude-plugin/marketplace.json (the repo-root marketplace manifest). It is the single source of versions: each plugin is an entry in its plugins array, and there are no per-plugin plugin.json files.

  • Patch (0.2.0 -> 0.2.1): bug fixes, config changes, style cleanup
  • Minor (0.2.0 -> 0.3.0): new features, new hooks, new commands
  • Major (0.2.0 -> 1.0.0): breaking changes to hook behavior or config format

Before bumping

Compare the working-tree version against the version on origin/main:

git show origin/main:.claude-plugin/marketplace.json

If the plugin's version already differs from origin/main, it was already bumped for unreleased work. Do not bump again. Only bump when the working-tree version matches origin/main.

If both plugins changed, check each independently.

How to use it

Copy the folder

Take vinta/bump-plugin-version from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.