메뉴
Plugin release process for MAG Claude Plugins marketplace. Covers version bumping, marketplace.json updates, git tagging, and common mistakes. Use when releasing new plugin versions or troubleshooting update issues.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/MadAppGang/claude-code --skill release명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Use when starting isolated feature work or before executing implementation plans. Manages full worktree lifecycle from creation through cleanup with safety checks and error recovery.
Configuration reference and troubleshooting for the statusline plugin — sections, themes, bar widths, and script architecture
Common agent patterns and templates for Claude Code. Use when implementing agents to follow proven patterns for Tasks integration, quality checks, and external model invocation via claudish CLI.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | release |
| description | Plugin release process for MAG Claude Plugins marketplace. Covers version bumping, marketplace.json updates, git tagging, and common mistakes. Use when releasing new plugin versions or troubleshooting update issues. |
Complete guide for releasing new versions of plugins in the MAG Claude Plugins marketplace.
Claude Code plugin discovery works through TWO configuration files that MUST BOTH BE UPDATED:
plugins/{plugin-name}/plugin.json - The plugin's own version metadata.claude-plugin/marketplace.json - The marketplace catalog (what users see when browsing)Why both?
plugin.json - Defines the plugin itself (agents, commands, version)marketplace.json - The "catalog" that Claude Code reads for plugin discovery/plugin marketplace update which reads marketplace.jsonplugin.json, users won't see the new version!plugins/{plugin-name}/plugin.json - Update version fieldplugins/{plugin-name}/agents/*.md - Add new agents (if any)plugins/{plugin-name}/commands/*.md - Update commands (if any)plugins/{plugin-name}/skills/*/SKILL.mdCHANGELOG.md - Add new version entry at the topRELEASES.md - Add detailed release notes at the topCLAUDE.md - Update ALL version references (6+ locations)File: .claude-plugin/marketplace.json
Update TWO fields:
Marketplace metadata version (line ~10):
"metadata": {
"version": "3.3.0" // ← Update this
}
Specific plugin version (in plugins array):
"plugins": [
{
"name": "frontend",
"version": "3.3.0", // ← Update this (CRITICAL!)
"description": "..." // ← Update if description changed
}
]
# Commit all changes
git add -A
git commit -m "feat({plugin}): v{X.Y.Z} - {Feature summary}"
# Create tag (format: plugins/{plugin-name}/v{X.Y.Z})
git tag -a plugins/{plugin}/v{X.Y.Z} -m "..."
# Push
git push origin main
git push origin plugins/{plugin}/v{X.Y.Z}
/plugin marketplace update mag-claude-plugins
# Should show new version ✅
Symptom: Users still see old version after /plugin marketplace update
Fix:
# Update .claude-plugin/marketplace.json
vim .claude-plugin/marketplace.json
# Update plugins[].version field
git add .claude-plugin/marketplace.json
git commit -m "fix(marketplace): Update {plugin} version to v{X.Y.Z}"
git push origin main
Wrong: frontend-v3.3.0, v3.3.0, frontend/v3.3.0
Correct: plugins/frontend/v3.3.0 ✅
Problem: plugin.json says v3.3.0 but marketplace.json says v3.2.0
Prevention: Use checklist, search for old version: grep -r "3.2.0" .
MAJOR (X.0.0): Breaking changes (removed agents, changed behavior) MINOR (x.Y.0): New features (new agents/commands, backward compatible) PATCH (x.y.Z): Bug fixes (no new features, backward compatible)
Minimal checklist:
plugins/{plugin}/plugin.json version.claude-plugin/marketplace.json plugin version ⚠️ CRITICALCHANGELOG.md, RELEASES.md, CLAUDE.mdgit commit -m "feat({plugin}): v{X.Y.Z} - {summary}"git tag -a plugins/{plugin}/v{X.Y.Z} -m "..."git push origin main && git push origin plugins/{plugin}/v{X.Y.Z}/plugin marketplace update shows new version# 1. Update versions
vim plugins/frontend/plugin.json # version: "3.3.0"
vim .claude-plugin/marketplace.json # plugins[0].version: "3.3.0" ← DON'T FORGET!
vim CHANGELOG.md RELEASES.md CLAUDE.md
# 2. Commit
git add -A
git commit -m "feat(frontend): v3.3.0 - Multi-Model Plan Review"
# 3. Tag
git tag -a plugins/frontend/v3.3.0 -m "Frontend Plugin v3.3.0"
# 4. Push
git push origin main
git push origin plugins/frontend/v3.3.0
# 5. Verify
/plugin marketplace update mag-claude-plugins
# Output: frontend v3.3.0 ✅
Q: Users still see old version
A: Check .claude-plugin/marketplace.json - version must match plugin.json
Q: Tag already exists
A: git tag -d {tag} then git push origin :{tag} then recreate
Q: How to test locally?
A: /plugin marketplace add /path/to/claude-code
Related: RELEASE_PROCESS.md - Full detailed documentation
Last Updated: November 13, 2025