release

Name: release
Availability: InStock
Author: MadAppGang

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

278|29|Updated Nov 4, 2025

Search Tags:#versioning #plugin #release #marketplace #git-tagging

Ready to run

npx skills add https://github.com/MadAppGang/claude-code --skill release-madappgang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/MadAppGang/claude-code/tree/main/skills/release
Command: npx skills add https://github.com/MadAppGang/claude-code --skill release-madappgang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides plugin release for MAG Claude Plugins marketplace, covering version bumps, marketplace.json updates, git tagging, and common pitfalls. It helps avoid inconsistent versions and misconfigurations during release.

Core Features & Use Cases

Release Checklist: Step-by-step process to prepare plugin files, documentation, and marketplace entries.
Version Consistency: Ensures both plugin.json and marketplace.json are updated together to surface new versions.
Troubleshooting Aid: Diagnostics for common marketplace update mistakes and tag formats.

Quick Start

Run the release workflow to publish a new plugin version, then verify with /plugin marketplace update.

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 my MAG Claude Plugin?▼

Release a plugin version by updating both plugin.json and marketplace.json with the new version number, creating a git tag, and running /plugin marketplace update to verify the changes sync to the marketplace catalog.

Why is my plugin version not showing up in the marketplace after release?▼

Version mismatches between plugin.json and marketplace.json prevent marketplace updates. Ensure both files are updated together with identical version numbers, then verify with /plugin marketplace update.

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

Git tagging for plugin releases follows a specific format to maintain release auditability. Check the release checklist for the correct tag structure and ensure consistency across all plugin releases.

Can I automate version bumps and marketplace synchronization for my plugins?▼

The release workflow coordinates version bumps and marketplace.json synchronization automatically through the release checklist, enforcing dual-file updates and maintaining version consistency without manual errors.

How do I troubleshoot failed marketplace updates after tagging a release?▼

Run /plugin marketplace update to diagnose marketplace update issues. Common causes include inconsistent versions between plugin.json and marketplace.json, or incorrect git tag formats.

Do I need to manually edit marketplace.json every time I release a plugin?▼

Yes, marketplace.json must be updated alongside plugin.json during release. The release checklist ensures both files are modified together to prevent version inconsistencies and marketplace publication failures.