test-setup

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

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill test-setup-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/test-setup
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill test-setup-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffold a complete test infrastructure for engine projects, including test directories, engine-specific runners, and CI workflows, so you can bootstrap reliable quality gates with minimal setup.

Core Features & Use Cases

  • Create tests/ layout with unit, integration, smoke, and evidence folders
  • Generate engine-specific test runners and CI workflows
  • Preserve existing files while creating missing infrastructure, enabling safe re-runs

Quick Start

Run /test-setup to scaffold the full test infrastructure for your engine.

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 CI and test infrastructure for a game engine project?

Test infrastructure for engine projects is scaffolded automatically by creating test directories, engine-specific runners, and GitHub Actions workflows. This generates unit, integration, and CI test layouts to bootstrap reliable quality gates.

What is included in a scalable test infrastructure setup?

A scalable test infrastructure setup includes a tests directory layout with unit, integration, smoke, and evidence folders, alongside engine-specific test runners and CI workflows to establish reliable quality gates.

Can I generate GitHub Actions workflows for unit and integration tests without losing existing files?

Yes, generating GitHub Actions workflows and test runners preserves existing files. The setup creates only missing infrastructure, enabling safe re-runs without overwriting your current project data.

When should I bootstrap automated test runners and CI workflows for engine testing?

You should bootstrap automated test runners and CI workflows as a one-time technical setup before your first sprint. This ensures scalable quality gates are established early for unit, integration, and smoke testing.

Does this automated test setup work for existing software engine projects?

Yes, the automated test setup works for existing software engine projects by preserving current files and only creating missing infrastructure. This enables safe re-runs to add unit, integration, and CI tests.