Skip to content
SkillModel-led1,961 tokens in use

godot-gdscript-headless-testing

Runs Godot 4.7 GDScript tests with godot --headless and a SceneTree runner that returns a meaningful exit code, so CI jobs can gate merges.

9,684 stars on the repository Apache License 2.0gamedev-skills/awesome-gamedev-agent-skills · skills/godot/godot-gdscript-headless-testing
npx skills add gamedev-skills/awesome-gamedev-agent-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing godot-gdscript-headless-testing costs

103tokens idle
1,961tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity92
  • Maintenance96
  • Community60
  • Maturity24
  • Momentum40

This skill shows an agent how to run GDScript tests from a terminal or CI and get a process exit code that means something. Its central rule is that Godot’s exit code reflects only what the runner passes to quit(), because script errors, push_error() and failed assert() calls leave it at zero.

It gives a SceneTree test runner that counts failures itself and ends with quit(1) on any failure, a variant for tests that wait on frames, timers or signals, and a GitHub Actions job with an import step and a timeout. It also tells the agent to break one assertion on purpose and confirm the exit code changes before trusting a green run.

What You Get

  • A seven-step workflow from checking the binary to verifying that the runner can fail
  • A minimal SceneTree runner that counts failures and exits non-zero
  • A runner pattern for tests that wait on a frame, a timer or a signal
  • A GitHub Actions job with an import step, a step timeout and log output on failure

Common Use Cases

  • Adding GDScript unit tests to a GitHub Actions workflow
  • Fixing a CI job that hangs after a failed assert
  • Finding why a test run exits 0 even though the log shows SCRIPT ERROR lines
  • Smoke-running a scene for a few hundred frames and scanning the log

What Makes It Unique

The skill is built around one fact that most test setups miss: Godot errors do not change the exit code. It therefore uses a counter helper, a loop that treats a test that died halfway as a failure, and a final check that a deliberately broken assertion produces exit code 1. It also records hang causes such as a bare assert before quit() and an await on a freed signal source.

Under The Hood

The agent loads the SKILL.md only; the skill ships no scripts or reference files. It tells the agent to run commands in your project: the Godot binary headless to print its version, import the project and run the runner script or a scene, with stdout and stderr redirected to log files that are searched with grep. It also has the agent write a test runner file and, if asked, a GitHub Actions workflow step. It reads and writes project files; it makes no network calls.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers