releasing-godot-prompter

Automates version bumps, tagging, and marketplace manifest updates for GodotPrompter releases.

657|31|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/jame581/GodotPrompter --skill releasing-godot-prompter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasing-godot-prompter
Source: https://github.com/jame581/GodotPrompter/tree/main/.claude/skills/releasing-godot-prompter
Command: npx skills add https://github.com/jame581/GodotPrompter --skill releasing-godot-prompter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a new version of GodotPrompter requires keeping multiple version files in sync (package.json, plugin.json, marketplace.json), updating the changelog, tagging correctly, and ensuring marketplace PRs are opened — a process that is easy to get wrong when done manually.

Core Features & Use Cases

  • Version Bump Automation: Runs node scripts/bump-version.mjs <version> to update package.json, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, and sibling marketplace manifests, including syncing the live skill count in manifest descriptions.
  • Tag-Triggered Release Workflow: Committing, tagging with v<version>, and pushing triggers .github/workflows/release.yml, which validates, creates the GitHub release, and opens marketplace PRs when MARKETPLACE_TOKEN is configured.
  • Use Case: When cutting release v1.10.0, follow the sequence to bump all manifests, update CHANGELOG.md, tag, and push — then manually bump the skillsmith and godot-prompter-marketplace manifests if the workflow's marketplace step is skipped.

Quick Start

Ask the agent to cut a new GodotPrompter release for version 1.10.0 following the version-bump and tagging sequence.

Frequently Asked Questions about releasing-godot-prompter

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release a new version of GodotPrompter?

Run node scripts/bump-version.mjs with the new version, update CHANGELOG.md, then commit, tag with v<version>, and push with tags. The release workflow validates, creates the GitHub release, and opens marketplace PRs.

How do I bump the GodotPrompter version across all manifests?

Run node scripts/bump-version.mjs <version>. It updates package.json, .claude-plugin/plugin.json, .claude-plugin/marketplace.json, and sibling marketplaces, and syncs the live skill count into each manifest description.

Which files must have matching versions before tagging a release?

package.json and .claude-plugin/plugin.json must match, and the root plugin.json for Antigravity must match package.json too. The bump script handles these, but verify before tagging.

What happens if the release workflow marketplace step is skipped?

Manually bump skillsmith/.claude-plugin/marketplace.json (primary) and the legacy godot-prompter-marketplace/.claude-plugin/marketplace.json. Auto-opened marketplace PRs also need manual review approval on the sibling repos.

Why does the release workflow not open marketplace PRs?

Marketplace PRs are only opened when MARKETPLACE_TOKEN is configured in the repository. Without it, the marketplace step is skipped and the sibling marketplace manifests must be bumped manually.