mcpField
R
releasing-godot-prompter

releasing-godot-prompter

github.com/jame581Development88997 installsUpdated 5d ago
Repository

About releasing-godot-prompter

This skill documents the release process for the GodotPrompter plugin, for maintainers preparing releases. It covers version synchronization, documentation updates, branch merging, tagging, and follow-up workflow checks.

Key features

  1. 01Sync versions across files
  2. 02Refresh the token budget table
  3. 03Maintain the changelog
  4. 04Release through branches and tags
  5. 05Update marketplace manifests

Use cases

  1. 01Preparing a GodotPrompter release
  2. 02Checking plugin manifest version consistency
  3. 03Updating marketplace manifests after release

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/jame581/godotprompter --skill releasing-godot-prompter

After installing, type/releasing-godot-prompterin Claude Code to confirm it loaded.

Details

From the project README

Releasing GodotPrompter

Current version: check package.json and .claude-plugin/plugin.json (must match). Full command sequence lives in CONTRIBUTING.md.

Sequence

  1. node scripts/bump-version.mjs <version> — bumps all five files release.yml verifies (package.json, the root plugin.json (Antigravity), .claude-plugin/plugin.json, .claude-plugin/marketplace.json, .cursor-plugin/plugin.json), plus sibling marketplaces if present; also syncs the live skill count into the "N domain-specific skills" text of each manifest description.
  2. Do the two things the bump script does not touch:
    • regenerate the table in docs/token-budget.md (npm ci --prefix scripts && node scripts/count-tokens.mjs --tokenizer --markdown, pasted between the TOKEN-TABLE markers) and fix the skill/agent counts in the intro above them;
    • set the Grok "pin to a release" example in README.md to the new tag — it sat at v1.11.0 through three releases.
  3. Update CHANGELOG.md with the new section.
  4. Commit on a release/v<version> branch, open a PR and merge it (master is protected by the "Protect master" ruleset: no direct push). Then tag the merge commit on master with an annotated tag (git tag -a v<version>) and git push origin v<version> — .github/workflows/release.yml then validates, creates the GitHub release, commits the plugin-only bundle to the plugin-bundle branch (what Anthropic's plugin directory and both marketplaces install from), and opens marketplace PRs that point the entry at "ref": "plugin-bundle" (when MARKETPLACE_TOKEN is configured). Merge those PRs only after plugin-bundle has the tag's commit.
  5. If the workflow's marketplace step is skipped, manually bump skillsmith/.claude-plugin/marketplace.json (primary) and the legacy godot-prompter-marketplace/.claude-plugin/marketplace.json.

Notes

  • The root plugin.json (Antigravity) must match package.json too — step 1 handles it, but verify before tagging.
  • Auto-opened marketplace PRs need manual review approval on the sibling repos.
  • Reset local sibling clones before pushing to avoid conflicts.

Comments

Markdown supported