bump-versions

Sync plugin.json versions and create per-plugin git tags for releases.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill bump-versions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-versions
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/.claude/skills/bump-versions
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill bump-versions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

## What problem does it solve? Bump-versions keeps plugin.json version fields in sync with code changes across all plugins, and automatically creates per-plugin git tags to signal releases to clients and tooling.

## Core Features & Use Cases

  • Detects changed plugins since the last per-plugin tag and reports current versions.
  • Recommends and applies the appropriate semver bump, updates manifests, commits changes, and creates tags.
  • Generates a final release-ready report and detects new marketplace entries to simplify publishing.

### Quick Start Run the bump-versions skill to scan for changes, bump affected plugin manifests, and tag releases.

Frequently Asked Questions about bump-versions

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

FAQPage Schema
How do I automatically bump versions in plugin.json files after code changes?

To automatically bump versions in plugin.json files, this skill scans for changed plugins since the last git tag, recommends the appropriate semver bump, updates the manifests, and commits the changes.

How does git tagging work for releasing multiple plugins in a single repository?

Git tagging for multiple plugins works by creating per-plugin git tags to signal releases. The skill detects changed plugins, applies version bumps to plugin.json, and generates the specific tag names for each release.

Do I need jq installed to automate semver bumps and git tags for plugins?

Yes, you need jq and git installed in your environment. The skill relies on jq to read and manipulate current version fields across the plugin.json manifest set and git to commit changes and create tags.

What is the best way to keep plugin manifest versions in sync with code changes?

The best way to keep plugin manifest versions in sync is using an automated bump-versions workflow that detects changes since the last tag, applies the correct semver bump to plugin.json, and commits the updates.

Can I detect new marketplace entries when bumping plugin versions for release?

Yes, you can detect new marketplace entries when bumping plugin versions. The skill generates a final release-ready report that identifies new entries to simplify the publishing process for your plugin set.