skills.rest
tianzecn
tianzecnCOMMUNITY
Explore all skills by this author →
GitHub

release

Automate version bumps, marketplace.json updates, git tagging, and release documentation for MAG Claude Plugins.

2|Updated Dec 25, 2025
Search Tags:#git#workflow#versioning#plugin#release#marketplace
One-click install
npx skills add https://github.com/tianzecn/myclaudecode --skill release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/tianzecn/myclaudecode/tree/main/skills/release
Command: npx skills add https://github.com/tianzecn/myclaudecode --skill release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a complete, repeatable process for releasing new versions of Claude Plugins in the MAG Claude Plugins marketplace, including synchronized updates to plugin.json and marketplace.json, git tagging, and avoidance of common release mistakes.

Core Features & Use Cases

  • Release Checklist: ensure both plugins/{plugin-name}/plugin.json and .claude-plugin/marketplace.json are updated with the correct version.
  • Documentation Updates: guide updates to CHANGELOG.md, RELEASES.md, and CLAUDE.md to reflect new versions.
  • Marketplace Catalog Sync: critical two-file update to keep marketplace listings accurate for users.
  • Git Tagging & Verification: create proper tags and verify marketplace updates via CLI.

Quick Start

Update both plugin.json and marketplace.json to the new version, commit changes, create an annotated git tag under the format plugins/{plugin}/vX.Y.Z, push, and run the marketplace update check to verify the new version is visible.

Frequently Asked Questions about release

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

FAQPage Schema
How do I release a new version of a Claude Plugin to the marketplace?▼

Release a Claude Plugin by updating both plugin.json and marketplace.json with the new version number, committing changes, creating an annotated git tag in the format plugins/{plugin}/vX.Y.Z, pushing to the repository, and running the marketplace update check to verify the version is live.

Why do I need to update both plugin.json and marketplace.json for a release?▼

Both files must stay synchronized to keep the marketplace catalog accurate. plugin.json defines the plugin's local version, while marketplace.json drives what users see in the MAG Claude Plugins marketplace listing.

What's the correct git tag format for plugin releases?▼

Use the format plugins/{plugin-name}/vX.Y.Z where X.Y.Z is the semantic version. This standardized tagging ensures releases are properly tracked and discoverable in version history.

What files should I update when releasing a plugin version?▼

Update plugin.json and marketplace.json with the new version, then guide updates to CHANGELOG.md, RELEASES.md, and CLAUDE.md to document changes, fixes, and new features for users.

How do I verify a plugin release was successful?▼

Run the marketplace update check via CLI after pushing your tag and commits. This verifies the new version is visible and correctly indexed in the marketplace catalog.

Related Skills

Explore More Software Engineering Skills→
raineraine
2.1k

rebase

Rebase current branch onto main or specified origin branches with conflict resolution.

Community
Basic
pradyumnasagarpradyumnasagar
6

release-management

Manages ORS skill releases with versioning, changelogs, and marketplace updates.

Community
Intermediate
pigfootpigfoot
5

commit

Generate conventional Git commits with emoji prefixes and GPG signing.

Community
Advanced
MadAppGangMadAppGang
278

release

Coordinate plugin version bumps, marketplace.json updates, and git tagging.

Official
Advanced