marketplace-release

Automate per-plugin version releases for Claude Code marketplaces.

4|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Emasoft/ghe-marketplace --skill marketplace-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: marketplace-release
Source: https://github.com/Emasoft/ghe-marketplace/tree/main/plugins/marketplace-utils/skills/marketplace-release
Command: npx skills add https://github.com/Emasoft/ghe-marketplace --skill marketplace-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Use when creating releases for Claude Code plugin marketplaces. Supports independent plugin versioning - each plugin can be released separately.

Core Features & Use Cases

  • Prerequisites check: gh CLI authenticated and git clean state
  • Version bumping: Update marketplace.json and plugin.json per plugin
  • Script version updates: Optional update for marketplace-utils
  • Release artifacts: Commit, tag, push, and create GitHub release

Quick Start

  • Patch release for ghe: python "${CLAUDE_PLUGIN_ROOT}/scripts/release.py" patch ghe "Fix avatar loading issue"
  • Minor release for marketplace-utils: python "${CLAUDE_PLUGIN_ROOT}/scripts/release.py" minor marketplace-utils "Add TOC generator"

Frequently Asked Questions about marketplace-release

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

FAQPage Schema
How do I automate releasing individual plugins in a multi-plugin marketplace?

Marketplace-release automates per-plugin versioning and releases by handling version bumps in marketplace.json and plugin.json, generating commit tags, pushing to remote, and creating GitHub releases—each plugin releases independently on its own schedule.

What version bump types does the release process support?

The release automation supports patch, minor, and major version bumps per plugin, preserving version suffixes like -alpha or -beta while updating plugin metadata and generating release artifacts.

What prerequisites must be met before running a plugin release?

The gh CLI must be authenticated and your git working state must be clean—the automation validates these conditions before proceeding with version bumps, tagging, and GitHub release creation.

Can I update marketplace-utils scripts as part of the release workflow?

Yes, the release process includes optional script version updates for marketplace-utils alongside per-plugin version bumping in marketplace.json and plugin.json.

Does the release automation update documentation and badges?

The automation handles README and badge updates as part of the release workflow, along with commit creation, tagging, and remote pushes to maintain consistent documentation across releases.