test-setup

Create test directories, engine runners, and GitHub Actions workflows.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill test-setup-xganqaq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios/tree/main/.claude/skills/test-setup
Command: npx skills add https://github.com/XGanQAQ/Unity-Claude-Code-Game-Studios --skill test-setup-xganqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the chaos of manually setting up testing and CI by scaffolding a consistent test framework structure and GitHub Actions workflow across engine types.

Core Features & Use Cases

  • Engine-aware detection: Reads your configured engine from .claude/docs/technical-preferences.md and chooses the right runner artifacts.
  • Opinionated test layout: Creates tests/ with unit/, integration/, smoke/, evidence/, plus a tests/README.md that documents conventions and evidence expectations.
  • CI/CD wiring: Generates .github/workflows/tests.yml so tests run on every push and pull request without you remembering to trigger them.
  • Safety-first creation: Detects existing infrastructure and, unless you pass force, stops early when everything appears already present; it also never overwrites existing files.

Quick Start

Run test scaffolding with the command: /test-setup force.

Frequently Asked Questions about test-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up unit tests and GitHub Actions CI for a Godot, Unity, or Unreal project?

This Skill scaffolds automated testing infrastructure by creating a standardized tests directory layout, engine-specific runners, and a GitHub Actions workflow to initialize unit, integration, smoke, and evidence workflows.

Can I automatically create a test directory structure with unit, integration, and smoke tests?

Yes, automated test scaffolding creates an opinionated test layout featuring unit, integration, smoke, and evidence folders, along with a README documenting conventions and evidence expectations for your engine project.

Does the test scaffolding support existing CI workflows without overwriting files?

Yes, the CI scaffolding detects existing test infrastructure and stops early unless the force command is passed, ensuring it never overwrites existing files and only produces missing test runners or workflow artifacts.

How do I wire GitHub Actions to run engine-specific smoke tests on every push?

You can wire CI by generating a .github/workflows/tests.yml file that triggers on push and pull requests, automatically executing the correct engine test commands for your Godot, Unity, or Unreal project.

What is needed to initialize engine-specific test runners for my game project?

Initializing engine-specific test runners requires reading your configured engine from technical preferences, detecting existing CI artifacts, and requesting approval before writing the missing test files to your project.