test-setup

Scaffold tests/ and generate engine-specific CI runners for a game engine project.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill test-setup-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/test-setup
Command: npx skills add https://github.com/WindXRan/y3td --skill test-setup-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone setup of an automated test framework and continuous integration workflow by generating a consistent, engine-aware testing scaffold with sensible defaults.

Core Features & Use Cases

  • Engine detection & safety checks: Reads the configured engine from .claude/docs/technical-preferences.md, verifies existing tests/ and engine-specific runner artifacts, and stops if the engine is not configured.
  • Project scaffolding & CI wiring: Creates the standard tests/ directory structure, generates engine-specific runner configuration and placeholders, and produces .github/workflows/tests.yml to run tests on every push to main.
  • Smoke test seed: Adds tests/smoke/critical-paths.md as a reusable critical-path checklist to gate QA hand-offs.

Quick Start

Run /test-setup during the Technical Setup phase to create the test directory structure and the CI workflow, then approve the planned file creation.

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 automated testing and CI/CD for my game engine project?

Scaffold tests and CI/CD by generating a tests/ directory, engine-specific runners, and a GitHub Actions workflow to execute tests automatically on every push to main.

Do I need to configure my game engine before generating test runners?

Yes, you must configure your target game engine in the .claude/docs/technical-preferences.md file beforehand. The scaffolding process reads this configuration to generate matching engine-specific runners and stops if the engine is not configured.

Will generating test scaffolding overwrite my existing tests directory?

No, generating test scaffolding will not overwrite existing files. The process detects existing test states and runner artifacts, prompts for approval, and only creates missing directories and files without overwriting your current setup.

What is a smoke test seed and how does it gate QA hand-offs?

A smoke test seed is a critical-path checklist created at tests/smoke/critical-paths.md. It provides a reusable baseline checklist to verify essential functionality and gate quality assurance hand-offs before broader testing.

How does CI pipeline integration work for repository test scaffolding?

CI pipeline integration works by producing a .github/workflows/tests.yml file. This GitHub Actions workflow automatically runs your scaffolded tests on every push to the main branch to ensure continuous workflow readiness.