marketplace-release
Automate plugin marketplace releases
Managing plugin releases manually is error-prone and inconsistent. This skill automates the entire release workflow including version bumps, git tags, commit messages, and GitHub releases with proper changelog links.
スキルZIPをダウンロード
Claudeでアップロード
設定 → 機能 → スキル → スキルをアップロードへ移動
オンにして利用開始
テストする
「marketplace-release」を使用しています。 Release a patch for ghe with message: Fix avatar loading issue
期待される結果:
- Marketplace: ghe-marketplace
- Plugin: ghe
- Current version: 0.5.4
- New version: 0.5.5
- Proceeding with release ghe-v0.5.5? [y/N]
「marketplace-release」を使用しています。 List all plugins with their versions
期待される結果:
- Marketplace: ghe-marketplace
- Plugin Version Source
- --------------------------------------------------
- ghe 0.5.4 ./plugins/ghe
- marketplace-utils 1.0.0 ./plugins/marketplace-utils
セキュリティ監査
安全The skill consists solely of documentation (SKILL.md) describing a release automation script. Static findings of external commands, network access, and weak cryptography are all false positives. The skill file contains only documentation with bash command examples - no executable code exists in the skill itself. All detected patterns are safe documentation examples showing legitimate GitHub CLI and Python script usage.
リスク要因
⚡ スクリプトを含む (1)
📁 ファイルシステムへのアクセス (3)
品質スコア
作れるもの
Release a bug fix patch
Quickly release a patch version after fixing a bug. The skill bumps the version, creates a git tag, and publishes the release to GitHub with your commit message as release notes.
Publish a new feature release
Release a minor version with new features. The skill updates all version references, creates release documentation, and pushes changes to remote with proper tagging.
Coordinate a breaking change release
Safely release a major version with breaking changes. The skill validates the plugin, updates all version markers, and creates a properly formatted release with upgrade instructions.
これらのプロンプトを試す
Release a patch version for the [plugin-name] plugin with the message: "[your fix description]"
Release a minor version for [plugin-name]. The release notes should describe: [feature descriptions]
Release a major version for [plugin-name]. This is a breaking change. Include these upgrade instructions: [migration steps]
List all plugins in this marketplace with their current versions and sources
ベストプラクティス
- Validate your plugin before release using the validation script to catch configuration errors early
- Run releases from a clean git state to ensure the release commit contains only intentional changes
- Use semantic versioning: patch for fixes, minor for features, major for breaking changes
回避
- Do not skip the confirmation prompt without reviewing the version changes first
- Do not run releases from plugin subdirectories instead of the marketplace root
- Do not forget to authenticate with GitHub CLI (gh auth login) before attempting releases