check-versions

Verify plugin version bumps and marketplace.json consistency after branch changes.

2|2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/cboone/agent-harness-plugins --skill check-versions-cboone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: check-versions
Source: https://github.com/cboone/agent-harness-plugins/tree/main/.claude/skills/check-versions
Command: npx skills add https://github.com/cboone/agent-harness-plugins --skill check-versions-cboone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When maintaining a plugin marketplace repository, it is easy to forget to bump a plugin's version after changing its files, or to let marketplace.json drift out of sync with the actual plugin directories. This Skill audits the current branch against its merge base and reports every version and registration inconsistency before you merge or open a PR. ## Core Features & Use Cases - Version Bump Detection: Compares each changed plugin's plugin.json version against the merge base and flags missing, regressed, or invalid version bumps. - Marketplace Sync Validation: Verifies every plugins/ directory has a marketplace entry, every entry points to a real plugin, and version fields live only in plugin manifests. - Codex Manifest Cross-Check: Ensures .codex-plugin/plugin.json versions match their Claude counterparts when both exist. - Use Case: After merging main into your feature branch, run the check to confirm all modified plugins received appropriate semver bumps and marketplace.json is fully synchronized before creating a pull request. ## Quick Start Ask the assistant to check versions and verify that all plugin version bumps and marketplace entries are correct on the current branch.

Frequently Asked Questions about check-versions

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

FAQPage Schema
How do I check if plugin versions were bumped correctly on a branch?▼

Run the version check, which diffs the current branch against its merge base with the default branch. It reads each changed plugin's plugin.json at both revisions and flags any plugin whose content changed without a corresponding version bump.

How to validate marketplace.json against plugin directories?▼

The check reads .claude-plugin/marketplace.json and verifies coverage in both directions: every plugins/ directory must have a marketplace entry, and every entry must point to an existing plugin directory. It also confirms version fields appear only in plugin manifests.

What semver bump level should a plugin change get?▼

Wording-only or prompt changes warrant a patch bump, new files or capabilities warrant a minor bump, and deleted or restructured skill or hook files warrant a major bump. New plugins should start at version 1.0.0.

Does the version check work without the GitHub CLI?▼

Yes. If the gh command is unavailable, it falls back to detecting the default branch via git rev-parse on origin/HEAD. All other comparisons use plain git commands like merge-base, diff, and show.

What happens when the branch has no divergent commits?▼

When HEAD equals the merge base, the check compares against the state before the most recent merge instead, using the first parent of the latest merge commit as the comparison base.