agentleFS
yurineko73yurineko73/Godot-MCP-Native/skills/release/SKILL.md

release

Skill836 starsChanged 6 months agoMITView on GitHub

Automate Godot MCP Native plugin and CLI release. Bumps versions, runs tests, builds packages, creates GitHub Release draft.

  • Commits and pushes

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when asked to release a new version of the Godot MCP Native plugin and gdmcp CLI.

    line 8
  2. Very specific:

    Use -DryRun to preview without changes.

    line 33
  3. Very specific:

    Commit version bump: git commit -m "chore: bump version to X.Y.Z"

    line 53
  4. Very specific:

    If gh release create fails, check gh auth status

    line 68
  5. Very specific:

    If Rust tests fail, run cargo test --manifest-path cli/gdmcp/Cargo.toml directly

    line 69
  6. Distinctive:

    If GUT fails, open the project in Godot editor and run tests interactively

    line 70
  7. Very specific:

    If packaging tests fail, check test/integration/test_gdmcp_packaging.py

    line 71

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “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

Release Godot MCP Native

Use this skill when asked to release a new version of the Godot MCP Native plugin and gdmcp CLI.

Prerequisites

  • Rust toolchain installed at .gdmcp/ (or system-wide cargo)
  • Godot 4.6.1 at F:\Godot\Godot_v4.6.1-stable_win64.exe
  • Python 3 with test/integration/ dependencies
  • gh CLI authenticated with yurineko73/Godot-MCP-Native repo access

Workflow

1. Run the release script

.\scripts\release.ps1 -Version <X.Y.Z>

This automates:

  • Version bump in plugin.cfg, cli_release.json, mcp_types.gd, Cargo.toml
  • Full test suite (Rust tests + clippy + GUT + packaging)
  • CLI package build (Windows x64; Linux/macOS built separately)
  • Plugin archive (dist/godot-mcp-native-X.Y.Z.zip)
  • GitHub Release draft with artifacts uploaded

Use -DryRun to preview without changes. Use -SkipTests for quick iteration.

2. Build other platform packages (on their respective hosts)

# Linux
./cli/gdmcp/scripts/package.sh X.Y.Z x86_64-unknown-linux-gnu

# macOS
./cli/gdmcp/scripts/package.sh X.Y.Z x86_64-apple-darwin
./cli/gdmcp/scripts/package.sh X.Y.Z aarch64-apple-darwin

Upload the resulting zip files to the GitHub Release draft.

3. Manual steps

  • Submit godot-mcp-native-X.Y.Z.zip to Godot Asset Library
  • Upload packages to Quark cloud drive (share link pre-configured in cli_release.json; update only if Quark generates a new link)
  • Publish the GitHub Release draft
  • Commit version bump: git commit -m "chore: bump version to X.Y.Z"

4. Verify the release

After publishing:

# Install from GitHub Release
gdmcp --json doctor

# Verify the plugin panel shows correct version in Godot editor

Troubleshooting

  • If gh release create fails, check gh auth status
  • If Rust tests fail, run cargo test --manifest-path cli/gdmcp/Cargo.toml directly
  • If GUT fails, open the project in Godot editor and run tests interactively
  • If packaging tests fail, check test/integration/test_gdmcp_packaging.py

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.