Run any Skill in Manus with one click

release-setup

Stars0

Forks0

UpdatedJune 9, 2026 at 15:16

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

bdfinst

bdfinst/plugin-builder

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

SKILL.md

readonly

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

/release-setup

Wire (or repair) release-please so every plugin releases independently and the catalog stays in lock-step automatically.

Before you start

Read ${CLAUDE_PLUGIN_ROOT}/knowledge/marketplace-conventions.md (§6).

Procedure

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.

More from this repository

same repository

add-plugin

bdfinst/plugin-builder

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.

2026-06-090

audit-plugin

bdfinst/plugin-builder

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.

2026-06-090

cloud-setup

bdfinst/plugin-builder

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.

2026-06-090

new-marketplace

bdfinst/plugin-builder

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.

2026-06-090

portability-check

bdfinst/plugin-builder

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).

2026-06-090

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

/release-setup

Wire (or repair) release-please so every plugin releases independently and the catalog stays in lock-step automatically.

Before you start

Read ${CLAUDE_PLUGIN_ROOT}/knowledge/marketplace-conventions.md (§6).

Procedure

"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.