mcpField
G
godot

godot

github.com/randroids-dojoDevelopment46358 installsUpdated 3w ago
Repository

About godot

godot is a skill for working with and verifying Godot projects according to their actual version, settings, and conventions. It covers test selection, build exports, and deployment checks, distinguishing static checks from runtime verification.

Key features

  1. 01Inspect project version and settings
  2. 02Choose GdUnit4 or PlayGodot tests
  3. 03Run project tests and parse results
  4. 04Export and inspect build artifacts
  5. 05Verify web builds in a browser
  6. 06Check the live target after deployment

Use cases

  1. 01Plan tests for an existing Godot project
  2. 02Automate scene input and end-to-end checks
  3. 03Verify platform or browser export builds
  4. 04Check CI changes and runtime state after deployment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/randroids-dojo/skills --skill godot

After installing, type/godotin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

.claude-plugin/
plugin.json
agents/
openai.yaml
references/
assertions.md
ci-integration.md
deployment.md
gdunit4-quickstart.md
playgodot.md
scene-runner.md
scripts/
export_build.py
parse_results.py
run_tests.py
validate_project.py

Details

From the project README

Godot

Work from the target project's actual Godot version, project settings, addons, and export presets. Preserve project conventions rather than imposing a generic scene architecture.

Preflight

  1. Read repository instructions and inspect project.godot, export_presets.cfg, installed addons, and the existing test layout.
  2. Resolve the Godot executable and verify its version before choosing commands or APIs.
  3. Determine the required verification level:
    • GdUnit4 for unit, component, and in-engine scene tests;
    • PlayGodot for external end-to-end automation, screenshots, or input simulation;
    • a real exported build when behavior depends on platform or browser packaging.
  4. Do not claim real-render, input, export, or deployment success from static checks alone.

Test and implement

Prefer the project's existing runner. A common GdUnit4 command is:

godot --headless --path . -s res://addons/gdUnit4/bin/GdUnitCmdTool.gd --run-tests

Use the bundled helpers by resolving them relative to this skill directory:

  • scripts/validate_project.py for project preflight;
  • scripts/run_tests.py for repeatable test execution;
  • scripts/export_build.py for exports;
  • scripts/parse_results.py for machine-readable test results.

Inspect helper options before running them, and do not overwrite a project's established commands when its own scripts are authoritative.

Export and deployment

  1. Read references/deployment.md when creating or changing export presets or deployment behavior.
  2. Export into the project's designated build directory and inspect the produced artifact.
  3. For web builds, serve the export and exercise it in a browser; verify asset loading, input, viewport behavior, console errors, and any required cross-origin isolation.
  4. Read references/ci-integration.md when changing CI rather than copying an unverified workflow example.
  5. Treat production deployment as a separate authorization boundary. After an authorized deployment, verify the live target rather than stopping at a successful CLI exit.

Finish with the Godot version, tests or runtime checks performed, produced artifact or deployment state, and any behavior that remains unverified.

Comments

Markdown supported