메뉴
Wire release-please with one package per plugin and the marketplace.json extra-files jsonpath sync, so plugin.json, the release tag, and the catalog entry can never drift. Use to set up or repair automated versioning + catalog sync.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Scaffold a new plugin inside an existing marketplace — the shipped dir skeleton, plugin.json, install.sh with the Git-Bash guard, settings.json, and CLAUDE.md; then register it in the catalog and in release-please packages with the catalog extra-files sync. Use when adding a plugin to a marketplace.
Audit a marketplace (or a single plugin) — run the shipping-hygiene sensor, structural checks (every catalog entry has a dir, every dir has a manifest, versions in sync), and the portability sweep. Reports findings and offers fixes. Use to validate a marketplace is healthy.
Generate the gated SessionStart install hook plus cloud-setup.sh and a "use skills directly" fallback so the marketplace is usable in Claude Code web/cloud sessions. Use to make a marketplace cloud-aware.
Scaffold a new Claude Code plugin-marketplace monorepo — catalog, repo-root tests/scripts/docs trees, CI workflows, release-please config, dev-setup, the hygiene sensor, and a root CLAUDE.md. Use when starting a fresh marketplace repository.
Run shellcheck -x over every shipped and dev shell script, flag bash-4/GNU-only constructs, verify env-bash shebangs, and check that each install.sh has the Git-Bash-on-Windows guard. Use to validate cross-platform portability (macOS bash 3.2 / BSD / Windows Git Bash).
| name | release-setup |
| description | Wire release-please with one package per plugin and the marketplace.json extra-files jsonpath sync, so plugin.json, the release tag, and the catalog entry can never drift. Use to set up or repair automated versioning + catalog sync. |
| user-invocable | true |
Wire (or repair) release-please so every plugin releases independently and the
catalog stays in lock-step automatically.
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/marketplace-conventions.md (§6).
Per-plugin package block. For every plugins/<name>/ with a manifest,
ensure release-please-config.json .packages["plugins/<name>"] matches the
template at
${CLAUDE_PLUGIN_ROOT}/templates/release/release-please-config.json
(with __NAME__ replaced). The extra-files must rewrite both the catalog
version and source.ref:
"extra-files": [
".claude-plugin/plugin.json",
{ "type": "json", "path": "/.claude-plugin/marketplace.json",
"jsonpath": "$.plugins[?(@.name=='<name>')].version" },
{ "type": "json", "path": "/.claude-plugin/marketplace.json",
"jsonpath": "$.plugins[?(@.name=='<name>')].source.ref" }
]
Manifest. Ensure .release-please-manifest.json has
"plugins/<name>": "<current manifest version>" for each plugin.
Workflow. Confirm .github/workflows/ has a release-please workflow
(add one calling googleapis/release-please-action if missing). Document
that feat: → minor, fix: → patch, feat!:/BREAKING CHANGE → major.
Verify + report. Validate the JSON (jq . release-please-config.json),
run bash scripts/structural-check.sh, and report. Never hand-edit catalog
versions/refs after this — the release flow owns them.