Agent skill

Godot Testing

A skill your agent uses when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C

MITAuto-check passedGame Development

Install Godot Testing

skills CLI

$ npx skills add jame581/GodotPrompter --skill godot-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install jame581/GodotPrompter godot-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/jame581/GodotPrompter.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/godot-testing .claude/skills/godot-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "godot-testing" agent skill from https://github.com/jame581/GodotPrompter/tree/master/skills/godot-testing into .claude/skills/godot-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "godot-testing", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/jame581/GodotPrompter/tree/master/skills/godot-testing

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add jame581/GodotPrompter --skill godot-testing -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jame581/GodotPrompter godot-testing --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jame581/GodotPrompter.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/godot-testing .agents/skills/godot-testing && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "godot-testing" agent skill from https://github.com/jame581/GodotPrompter/tree/master/skills/godot-testing into .agents/skills/godot-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "godot-testing", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jame581/GodotPrompter --skill godot-testing -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jame581/GodotPrompter godot-testing --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jame581/GodotPrompter.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/godot-testing .cursor/skills/godot-testing && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "godot-testing" agent skill from https://github.com/jame581/GodotPrompter/tree/master/skills/godot-testing into .cursor/skills/godot-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "godot-testing", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/jame581/GodotPrompter.git --path skills/godot-testing

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jame581/GodotPrompter --skill godot-testing -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jame581/GodotPrompter godot-testing --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jame581/GodotPrompter.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/godot-testing .gemini/skills/godot-testing && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "godot-testing" agent skill from https://github.com/jame581/GodotPrompter/tree/master/skills/godot-testing into .gemini/skills/godot-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "godot-testing", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install jame581/GodotPrompter godot-testing

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add jame581/GodotPrompter --skill godot-testing -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jame581/GodotPrompter.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/godot-testing .github/skills/godot-testing && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "godot-testing" agent skill from https://github.com/jame581/GodotPrompter/tree/master/skills/godot-testing into .github/skills/godot-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "godot-testing", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jame581/GodotPrompter --skill godot-testing -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jame581/GodotPrompter godot-testing --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jame581/GodotPrompter.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/godot-testing .opencode/skills/godot-testing && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "godot-testing" agent skill from https://github.com/jame581/GodotPrompter/tree/master/skills/godot-testing into .opencode/skills/godot-testing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "godot-testing", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: godot-testing
GitHub stars: 799
Token cost: ~2.4k tokens
SKILL.md length: 707 words
Files: 6 (incl. references)
Skills in repo: 58
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C

Writing tests for Godot projects — TDD workflow with GUT and gdUnit4
SKILL.md covers Framework Selection, TDD Workflow: RED-GREEN-REFACTOR, Test Directory Structure and Running Tests, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Covers both GDScript and C

What it does

Godot Testing is an agent skill from jame581/GodotPrompter. Use when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `gdunit4-reference.md`, `gut-reference.md` and `references/running-tests.md`).

It sits in Game Development, covering Game development and Test-driven development. It works with Godot and C#. The repository describes itself as: Agentic skills framework for Godot 4.x. Domain-specific skills for AI coding agents (Claude Code, Copilot, Antigravity, Cursor). The licence is MIT.

When your agent uses it

Writing tests for Godot projects — TDD workflow with GUT and gdUnit4
Covers both GDScript and C

Example prompts

“/godot-testing”

What it can do on your machine

Read from SKILL.md and the folder at commit 1e7d79d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Godot Testing loads about 2.4k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 30 tokens; SKILL.md has 707 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~30
When it runs · the whole SKILL.md, loaded when a task matches: ~2.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jame581/GodotPrompter at commit 1e7d79d, republished under its MIT licence (© jame581). 707 words, ~2,365 tokens.

Download SKILL.mdSave it as .claude/skills/godot-testing/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: godot-testing
description: Use when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C#

Godot Testing

This skill covers test-driven development (TDD) for Godot 4.3+ projects using GUT (Godot Unit Testing) and gdUnit4. It includes framework selection, full RED-GREEN-REFACTOR examples, test structure, running tests in CI, and common testing patterns.

Related skills: godot-code-review for review checklists, dependency-injection for test-friendly architecture, export-pipeline for CI/CD test automation.

Framework Selection

Feature	GUT	gdUnit4
Language	GDScript-first, limited C#	GDScript + C# (first-class)
Install	AssetLib or git submodule	AssetLib or git submodule
Editor integration	Built-in GUT panel	Built-in inspector + panel
Mocking	`double()` / `stub()` API	`mock()` / `spy()` API
Scene testing	`add_child_autofree()`	`auto_free()` + scene runner
CI support	`gut_cmdln.gd` CLI script	`gdunit4_runner` CLI script
C# support	Minimal (GDScript wrappers only)	Native C# assertions + lifecycle
Maturity	Established (Godot 3 + 4)	Godot 4 focused, actively updated
Best for	Pure GDScript projects	Mixed GDScript/C# or C#-only

Rule of thumb: Use GUT for GDScript-only projects. Use gdUnit4 for C# projects or when you need first-class C# support and scene runner utilities.

TDD Workflow: RED-GREEN-REFACTOR

The standard Test-Driven Development cycle: write a failing test (RED), write minimal code to pass (GREEN), then refactor without breaking the test. Each step has its own discipline — don't skip RED (you'll write tests that pass trivially), and don't skip REFACTOR (technical debt compounds).

See references/tdd-workflow.md for a worked GDScript + C# example walking through all three steps on a HealthComponent.

Test Directory Structure

res://
├── src/
│   └── components/
│       ├── health_component.gd
│       └── HealthComponent.cs
└── tests/
    ├── unit/
    │   ├── test_health_component.gd      # GUT: test_ prefix required
    │   └── HealthComponentTest.cs        # gdUnit4 C#: [TestSuite] attribute
    ├── integration/
    │   ├── test_player_scene.gd
    │   └── PlayerSceneTest.cs
    └── gut_config.json                   # GUT configuration (optional)

Naming conventions

Framework	GDScript file	C# file	Test method prefix/attribute
GUT	`test_*.gd`	N/A	`func test_*()`
gdUnit4	`test_*.gd`	`*Test.cs`	`func test_*()` / `[TestCase]`

Running Tests

Both frameworks ship a CLI runner. GUT: addons/gut/gut_cmdln.gd invoked via godot --headless --path . -s addons/gut/gut_cmdln.gd. gdUnit4: --add-gdunit-test-runner argument, or via the editor "GdUnit Tests" dock. CI: tag-triggered or PR-triggered GitHub Action that installs Godot, runs the suite, exits non-zero on failure.

See references/running-tests.md for full GUT and gdUnit4 CLI invocations + a copy-pasteable GitHub Actions workflow.

Testing Patterns

Four common patterns: scenes with nodes (instantiate via add_child in before_each, free in after_each), signal testing (assert that emitting works and connect-then-emit fires), mocking/doubling (gdUnit4 Mock<T> or hand-rolled fakes via @export injection), async (await yields, signals, frames in tests).

See references/testing-patterns.md for full code on each pattern (GDScript + C# where applicable).

Common Assertions

GUT assertions

Assertion	Description
`assert_eq(actual, expected)`	Equality
`assert_ne(actual, expected)`	Not equal
`assert_true(value)`	Is truthy
`assert_false(value)`	Is falsy
`assert_null(value)`	Is null
`assert_not_null(value)`	Is not null
`assert_gt(actual, expected)`	Greater than
`assert_lt(actual, expected)`	Less than
`assert_gte(actual, expected)`	Greater than or equal
`assert_lte(actual, expected)`	Less than or equal
`assert_has(collection, item)`	Collection contains item
`assert_does_not_have(collection, item)`	Collection does not contain item
`assert_string_contains(str, sub)`	String contains substring
`assert_almost_eq(actual, expected, margin)`	Float equality within margin
`assert_signal_emitted(obj, signal_name)`	Signal was emitted
`assert_signal_not_emitted(obj, signal_name)`	Signal was not emitted

Show full SKILL.md (275 more words)Show less

gdUnit4 assertions (GDScript + C#)

GDScript	C#	Description
`assert_that(val).is_equal(exp)`	`AssertThat(val).IsEqual(exp)`	Equality
`assert_that(val).is_not_equal(exp)`	`AssertThat(val).IsNotEqual(exp)`	Not equal
`assert_that(val).is_true()`	`AssertThat(val).IsTrue()`	Is true
`assert_that(val).is_false()`	`AssertThat(val).IsFalse()`	Is false
`assert_that(val).is_null()`	`AssertThat(val).IsNull()`	Is null
`assert_that(val).is_not_null()`	`AssertThat(val).IsNotNull()`	Is not null
`assert_that(val).is_greater(exp)`	`AssertThat(val).IsGreater(exp)`	Greater than
`assert_that(val).is_less(exp)`	`AssertThat(val).IsLess(exp)`	Less than
`assert_that(val).is_between(min, max)`	`AssertThat(val).IsBetween(min, max)`	In range (inclusive)
`assert_that(arr).contains([a, b])`	`AssertThat(arr).Contains(a, b)`	Array contains elements
`assert_that(str).contains("sub")`	`AssertThat(str).Contains("sub")`	String contains substring
`assert_that(val).is_approximately(exp, margin)`	`AssertThat(val).IsApproximately(exp, margin)`	Float within margin
`assert_signal(mon).is_emitted("name")`	`AssertSignal(mon).IsEmitted("name")`	Signal emitted

What NOT to Test

Avoid testing things that add noise without catching real bugs:

Godot engine internals — do not assert that Node.add_child() works or that @export variables show up in the editor
Private implementation details — test behavior through the public API; if a refactor breaks a test that covers only private state, the test is wrong
Visual/rendering output — pixel-level rendering results are brittle; test the data driving the visuals instead
Timing-sensitive floats without margins — use assert_almost_eq / IsApproximately for physics values
One-liners that wrap a built-in — a property getter that just returns a field needs no test
Every possible invalid input — test the documented contract, not every imaginable misuse

Checklist

Each test file matches the naming convention for the chosen framework (test_*.gd / *Test.cs)
Tests extend the correct base class (GutTest / GdUnit4.GdUnitTestSuite)
Nodes added to the scene tree use add_child_autofree or auto_free — never manual queue_free()
Signals are watched before the action that triggers them
Mocks/doubles are used for external dependencies, not for the unit under test
Each test covers exactly one behavior (one logical assertion per test)
CI workflow runs tests headlessly on every push and PR
Flaky async tests use explicit timeouts, not arbitrary sleep durations
Tests pass before merging (RED is only acceptable while actively implementing)

Files

SKILL.md and 5 other files (references) in skills/godot-testing of jame581/GodotPrompter.

SKILL.md
gdunit4-reference.md
gut-reference.md
references/running-tests.md
references/tdd-workflow.md
references/testing-patterns.md

Open the folder on GitHubat commit 1e7d79d

Compare with similar skills

Godot Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Godot Testing compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Godot Testing this skilljame581/GodotPrompter	799	—	~2.4k	Automated safety check: Pass	MIT	yesterday
Godot Admob App Openpoingstudios/godot-admob-plugin	632	—	~1k	Automated safety check: Pass	MIT	8 days ago
Godot Admob Bannerpoingstudios/godot-admob-plugin	632	—	~718	Automated safety check: Pass	MIT	8 days ago
Godot Admob Get Startedpoingstudios/godot-admob-plugin	632	—	~1k	Automated safety check: Pass	MIT	8 days ago
Godot Admob Interstitialpoingstudios/godot-admob-plugin	632	—	~1.1k	Automated safety check: Pass	MIT	8 days ago
Godot Admob Native Overlaypoingstudios/godot-admob-plugin	632	—	~1k	Automated safety check: Pass	MIT	8 days ago

Similar skills

Godot Admob App Open
poingstudios/godot-admob-plugin
Provides instructions to implement, load, show, and destroy App Open ads (shown on application startup or app resume) in GDScript and C.
632 GitHub stars~1k tokensUpdated 8 days ago
Game DevelopmentAuto-check passed
Godot Admob Banner
poingstudios/godot-admob-plugin
Provides instructions to implement, load, and destroy banner ads (AdView) using custom or adaptive sizes in GDScript and C.
632 GitHub stars~718 tokensUpdated 8 days ago
Game DevelopmentAuto-check passed
Godot Admob Get Started
poingstudios/godot-admob-plugin
Provides instructions to initialize the Godot AdMob SDK and configure user consent (UMP Flow) in GDScript and C.
632 GitHub stars~1k tokensUpdated 8 days ago
Game DevelopmentAuto-check passed
Godot Admob Interstitial
poingstudios/godot-admob-plugin
Provides instructions to implement, load, show, and destroy interstitial ads (full-screen image/text ads) in GDScript and C.
632 GitHub stars~1.1k tokensUpdated 8 days ago
Game DevelopmentAuto-check passed
Godot Admob Native Overlay
poingstudios/godot-admob-plugin
Provides instructions to implement, load, show, and destroy Native Overlay ads (customized/native-looking Control node template overlays) in GDScript and C.
632 GitHub stars~1k tokensUpdated 8 days ago
Game DevelopmentAuto-check passed
Stage Tamagotchi Godot Csharp
moeru-ai/airi
Apply the Stage Tamagotchi Godot C development method and code style when working in apps/stage-tamagotchi-kirie or its migration predecessor, engines/stage-tamagotchi-godot.
50k GitHub stars~677 tokensUpdated today
Game DevelopmentAuto-check passed

Questions about Godot Testing

What does Godot Testing do?

A skill your agent uses when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C. Godot Testing is an agent skill from jame581/GodotPrompter.

When should I use Godot Testing?

Godot Testing fits situations like: writing tests for Godot projects — TDD workflow with GUT and gdUnit4; covers both GDScript and C.

How do I install Godot Testing in Claude Code?

Run `npx skills add jame581/GodotPrompter --skill godot-testing -a claude-code`. Or copy the skill folder (skills/godot-testing in jame581/GodotPrompter) into .claude/skills/godot-testing in your project. Claude Code loads it when a task matches its description.

How do I install Godot Testing in Codex?

Run `npx skills add jame581/GodotPrompter --skill godot-testing -a codex`. Or copy the skill folder (skills/godot-testing in jame581/GodotPrompter) into .agents/skills/godot-testing in your project. Codex loads it when a task matches its description.

Can I use Godot Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jame581/GodotPrompter --skill godot-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/godot-testing, .gemini/skills/godot-testing, .github/skills/godot-testing and .opencode/skills/godot-testing in your project.

What does Godot Testing need to run?

SKILL.md names no scripts, command-line tools or credentials: Godot Testing is instructions for the agent only.

Does Godot Testing access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Godot Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Godot Testing use?

Godot Testing is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Godot Testing use?

About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.2k tokens, read only when the agent opens those files.

What are the alternatives to Godot Testing?

Skills that share tags, products or a category with Godot Testing: Godot Admob App Open (poingstudios/godot-admob-plugin, 632 stars), Godot Admob Banner (poingstudios/godot-admob-plugin, 632 stars), Godot Admob Get Started (poingstudios/godot-admob-plugin, 632 stars) and Godot Admob Interstitial (poingstudios/godot-admob-plugin, 632 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Godot Testing?

jame581 (a GitHub user) maintains it in jame581/GodotPrompter, which has 799 GitHub stars. The repository holds 58 skills in this directory. The repository was last updated on October 8, 2026.

Source: jame581/GodotPrompter on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Godot Testing

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Godot Testing

Framework Selection

TDD Workflow: RED-GREEN-REFACTOR

Test Directory Structure

Naming conventions

Running Tests

Testing Patterns

Common Assertions

GUT assertions

gdUnit4 assertions (GDScript + C#)

What NOT to Test

Checklist

Files

Compare with similar skills

Similar skills

More from jame581/GodotPrompter

Related

Questions about Godot Testing