What problem does it solve?
This Skill removes the friction of initializing automated testing for a game project by detecting the configured engine and creating a consistent test directory layout and CI workflow so teams don't delay writing tests.
Core Features & Use Cases
- Engine Detection: Reads .claude/docs/technical-preferences.md to determine whether the project uses Godot, Unity, or Unreal and tailors files accordingly.
- Test Scaffolding: Creates tests/, unit/, integration/, smoke/, evidence/, example runner files, and a tests/README.md to standardize test structure.
- CI Integration: Adds a .github/workflows/tests.yml configured per engine to run tests on pushes and pull requests; respects existing files and only creates missing artifacts unless forced.
- Use Case: Initialize test infrastructure during Technical Setup to ensure CI runs and test conventions are in place before the first sprint.
Quick Start
Run the test-setup skill once during Technical Setup to detect the engine and create tests/, engine-specific runner files, and a GitHub Actions workflow, adding the force argument to regenerate missing files without overwriting existing ones.