一键导入
releasing-plugin-versions
Use when releasing a new plugin version, bumping versions, creating git tags, or publishing GitHub releases for this marketplace
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when releasing a new plugin version, bumping versions, creating git tags, or publishing GitHub releases for this marketplace
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when encountering Swift 6 concurrency errors, Sendable conformance warnings, actor isolation issues, "global variable is not concurrency-safe" errors, or migrating codebases to Swift 6 language mode
Use when writing or enhancing Swift documentation comments for DocC generation, adding inline doc comments to Swift source files, or when user asks for API documentation
Use when setting up DocC documentation for a Swift package, deploying to GitHub Pages, or encountering "no such module 'UIKit'" during doc generation
Use when creating demo GIFs for Swift package READMEs, recording iOS simulator videos, or setting up demo apps for SwiftUI libraries
| name | releasing-plugin-versions |
| description | Use when releasing a new plugin version, bumping versions, creating git tags, or publishing GitHub releases for this marketplace |
metadata.version ≠ plugin version. These are DIFFERENT things:
| Field | What It Tracks | When to Update |
|---|---|---|
plugins[].version | Individual plugin version | Every plugin release |
metadata.version | Marketplace catalog structure | Adding/removing plugins ONLY |
Common mistake: Thinking metadata.version should "stay in sync" with plugin versions. It should NOT.
When releasing a plugin (e.g., swift 1.2.0 → 1.3.0):
plugins/swift/.claude-plugin/plugin.json → "version": "1.3.0".claude-plugin/marketplace.json → plugins[].version: "1.3.0"plugins/swift/README.md → Version section: 1.3.0README.md (root) → Available Plugins table: 1.3.0# 1. Stage changes
git add -A
# 2. Commit
git commit -m "Release swift v1.3.0
- Description of changes"
# 3. Tag (format: v1.3.0, NOT swift-v1.3.0)
git tag v1.3.0
# 4. Push
git push && git push origin v1.3.0
# 5. GitHub release
gh release create v1.3.0 --title "v1.3.0" --notes "## Changes
- Change 1
- Change 2
**Full Changelog**: https://github.com/OWNER/REPO/compare/v1.2.0...v1.3.0"
Use v1.3.0, NOT swift-v1.3.0. Check existing tags:
git tag --sort=-v:refname | head -5