agentleFS
jame581jame581/GodotPrompter/.claude/skills/releasing-godot-prompter/SKILL.md

releasing-godot-prompter

Skill965 starsChanged 27 days agoMITView on GitHub

Use when cutting a GodotPrompter release or bumping its version — the version-bump sequence, tag-triggered workflow, and the marketplace manifests that must follow.

  • Commits and pushes

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do the two things the bump script does not touch:

    line 18
  2. Very specific:

    Update CHANGELOG.md with the new section.

    line 24
  3. Very specific:

    Commit on a release/v<version> branch, open a PR and merge it (master is protected by the "Protect master" ruleset: no direct push).

    line 25
  4. Very specific:

    If the workflow's marketplace step is skipped, manually bump skillsmith/.claude-plugin/marketplace.json (primary) and the legacy …

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.