What problem does it solve? Setting up automated testing late in a game project is expensive and error-prone. This Skill scaffolds the complete test infrastructure—directory layout, engine-specific test runner configuration, and CI/CD pipeline—during the Technical Setup phase so tests run on every push from day one. ## Core Features & Use Cases - Engine Detection and Gating: Reads the configured engine from .ai-game-studio/project.json and refuses to proceed if the engine is not configured, redirecting to engine setup first. - Per-Engine Scaffolding: Generates GdUnit4 runner scripts for Godot, EditMode/PlayMode test folders for Unity, and Automation test guidance for Unreal Engine. - CI/CD Workflow Generation: Creates .github/workflows/tests.yml using the appropriate action (gdUnit4-action, game-ci/unity-test-runner, or a self-hosted UE runner). - Use Case: Before the first sprint of a Godot project, run this Skill to create tests/unit, tests/integration, tests/smoke/critical-paths.md, and a GitHub Actions workflow that blocks merges on failing tests. ## Quick Start Use $ai-game-studio:test-setup to scaffold the test framework and CI/CD pipeline for this project and report the created files.