Verify built Godot projects via headless checks, gdUnit4 tests, and static analysis.
npx skills add https://github.com/RandallLiuXin/GodotMaker --skill gm-verify
Please help me install this Agent Skill. Skill: gm-verify Source: https://github.com/RandallLiuXin/GodotMaker/tree/main/skills/core/gm-verify Command: npx skills add https://github.com/RandallLiuXin/GodotMaker --skill gm-verify
gm-verify eliminates the guesswork of whether a generated Godot project is actually correct by running automated, non-creative checks (headless build, unit tests, lint placeholders, and static analysis) against the latest built state.
Use the gm-verify skill to verify the most recent built project state by running: run /gm-verify.
High-intent search queries and answers about installing and using this skill.
Headless build verification and unit tests for a Godot project are executed by running deterministic mechanical checks via headless Godot execution. The process captures build-time errors, runs gdUnit4 tests, and emits a machine-readable verify_report.json.
gdUnit4 test reporting parsing is the extraction of pass/fail counts and failure details from automated unit tests run during a headless Godot build. This parsing generates a human-readable checklist summary and a machine-readable verify_report.json.
Godot static analysis catches issues beyond compilation by running ECS, test, and plan-oriented static checks against the built project state. These non-creative checks identify deeper structural problems without modifying game code or planning docs.
This verification workflow operates on a read-mostly basis with explicit invocation and guardrails. It is designed for safety-focused post-build validation and intentionally prevents modifying game code or planning docs during the mechanical checks.
A Godot headless build fails before unit tests when deterministic mechanical checks capture build-time errors during the initial headless Godot execution. This fast failure diagnosis prevents subsequent gdUnit4 tests and static analysis from running.
A pre-built Godot project state is required before running gm-verify. The skill applies automated mechanical checks, including headless execution, gdUnit4 unit tests, and static analysis, specifically against the latest built state to ensure project correctness.
minami110Execute GDUnit4 tests for Godot projects and write reports.
nilecuiDesign multi-stage CI/CD pipelines with approval gates and security checks.
XyrcesDesign BDD and TDD test workflows for ECS game systems and Godot behavior.
minami110Execute GDUnit4 tests and generate JSON reports for Godot projects.
