Skip to content
cccskills
FreePublished on GitHubEnglish overview

godot-testing

Add and run tests for Godot 4 GDScript games, from a small dependency-free check scene to gdUnit4 or GUT suites. The skill covers scene and signal checks, headless commands, and CI setup to catch broken behavior before a build is handed off.

OriginalShow the original description

Testing Godot 4 GDScript projects - a zero-dependency headless check scene, gdUnit4 and GUT suites, scene-runner tests, signal assertions, and CI commands. Use when adding tests to a Godot project, setting up CI, or proving a change did not break the game.

affaan-m/ECC305,197 stars(GitHub 305,197 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Adding the first tests to a Godot game
  • Writing gdUnit4 or GUT test suites
  • Running headless checks in CI
  • Checking whether a change broke a scene
  • Testing signals and simulated scene behavior

Overview

What it does

This skill covers ways to add tests to Godot 4 games written in GDScript and check their logic and scenes. A check scene with no add-ons can test conditions and return a failure exit code, so a shell or CI job can judge the result. If you need more features, the skill provides examples for gdUnit4 assertions, mocks, and scene runners, as well as GUT tests. It also covers headless startup checks, importing assets, and running tests in CI.

When it helps

Use it when adding tests to a Godot project for the first time or checking that a change has not broken the game before handing it off. It can also help automate checks for logic that does not depend on input, or run tests in CI. Tests that simulate input do not work in a standard headless run.

Example requests

  • “Create a check scene that verifies the inventory limit.”
  • “Write a gdUnit4 scene test for this Godot project.”
  • “Set up the steps for running Godot tests in CI.”

Notes

Using gdUnit4 or GUT requires installing the corresponding add-on. gdUnit4 tests that simulate input need a display; the examples include xvfb for Linux CI. In CI, import assets with --import before running tests.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodCommands run tests or import assets; destructive actions and external sending are not described.
Easy setupDoes it need few tools or API keys, and are they documented?
BPartly lackingA no-addon option is provided, but Godot and optional framework add-ons require setup.

Not counted in the score. Rated by AI (OpenAI Codex) as of Nov 18, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (1)

  • SKILL.md8.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummary

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC305.8KUpdated Oct 30, 2026

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC305.8KUpdated Oct 30, 2026

agent-eval

FreeSummary

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC305.8KUpdated Oct 30, 2026

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC305.8KUpdated Oct 30, 2026

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC305.8KUpdated Oct 5, 2026

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC305.8KUpdated Oct 30, 2026

See all skills by affaan-m

Report a problem with this skill