القائمة
Use when changing or releasing the godot-devtool MCP package itself, including tool catalog, build output, Godot addon, docs, and local Skill sync.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use with godot-devtool for live Godot editor operations through editor_ws, including selection, Inspector edits, UndoRedo scene changes, Dock status, and plugin reload.
Use with godot-devtool when installing the addon, checking plugin state, configuring a Godot project, or preparing export/project settings.
Use with godot-devtool for running Godot projects, runtime_ws game inspection, input simulation, screenshots, debug output, and run cleanup.
Use with godot-devtool for saved scene/resource/script authoring through native and headless Godot tools.
Use when MCP clients and connected AI assistants work on a Godot 4 project through the godot-devtool 3.2.1 MCP server.
| name | godot-devtool-release-verify |
| description | Use when changing or releasing the godot-devtool MCP package itself, including tool catalog, build output, Godot addon, docs, and local Skill sync. |
| metadata | {"version":"3.2.1","mcp_server":"godot-devtool"} |
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.