From godot-devtool
Verifies build, tool catalog, Godot addon, docs, and local Skill sync when editing or releasing the godot-devtool MCP package.
How this skill is triggered — by the user, by Claude, or both
Slash command
/godot-devtool:godot-devtool-release-verifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Load this when editing this MCP package rather than only using it on a Godot project.
Load this when editing this MCP package rather than only using it on a Godot project.
Run build-heavy verifiers sequentially:
npm.cmd run build
npm.cmd run verify:tools
npm.cmd run verify:skill
npm.cmd run verify:gdscripts
npm.cmd run verify:visualizer
npm.cmd run verify:plugin
npm.cmd run verify:runtime
npm.cmd run verify:process
npm.cmd run verify:security
npm.cmd run verify:all
For README tool table changes, run the generator after build and verify that English and Chinese tables stay in sync.
Use a real MCP stdio client or equivalent local MCP call chain:
get_capabilities
get_capabilities { "workflow": "live_editor", "includeSchemas": true }
get_capabilities { "includeSchemas": true }
Default get_capabilities must remain lightweight, include workflow summaries, omit schemas, and reject unfiltered schema requests.
Use E:/test or a fresh fixture:
plugin_install
plugin_status
run_project
get_game_node_properties
simulate_action
get_game_node_properties
stop_project
plugin_status
For editor validation, call plugin_dock_status and verify the structured GDT dock status instead of relying on editor screenshots.
After Skill edits:
npm.cmd run sync:skill
npm.cmd run verify:skill
The repo, build output, and installed Codex Skill copies must have matching version and content hashes.
npx claudepluginhub wangdiandao/godot-devtoolRoutes MCP tool discovery and dispatches to domain-specific skills for Godot 4 projects: project setup, live editor, runtime test, scene authoring, and release verification.
Standardizes Godot export, CI, and release packaging with reproducible presets and platform-aware validation. Useful when export presets are fragile or platform packaging issues recur.
Publishes a release end-to-end to npm, MCP Registry, GitHub Releases and GHCR after git wrapup is done. Retries transient network failures and reports partial state.