skills.rest
scomofo
scomofoCOMMUNITY
Explore all skills by this author →
GitHub

test-setup

Scaffold test directories and CI workflows for engine-based game repositories.

Updated Mar 28, 2026
Search Tags:#ci/cd#test automation#github actions#godot#test runner#gut#smoke testing
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill test-setup-scomofo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/test-setup
Command: npx skills add https://github.com/scomofo/dragon-forge --skill test-setup-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the friction of setting up reliable automated testing and continuous integration by generating a consistent test directory structure, engine-specific runner entry points, and a CI workflow that runs tests on every push.

Core Features & Use Cases

  • Engine detection and validation: Reads the configured engine from the project’s technical preferences and stops if the engine is not configured.
  • Idempotent scaffolding: Creates missing test directories and CI workflow files without overwriting existing test artifacts.
  • Godot/GUT-ready infrastructure: When using Godot, scaffolds a GdUnit4-compatible runner and a standard placement for unit and integration suites.
  • Smoke gate seeding: Adds a critical-path smoke test checklist for sprint/QA handoff readiness.
  • Use case: You’re starting a new technical setup phase and need tests to be runnable locally and automatically on GitHub Actions before the first sprint begins.

Quick Start

Ask the AI to run /test-setup during the Technical Setup phase to create the tests/ structure and the .github/workflows/tests.yml CI workflow.

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 for a Godot project?▼

Setting up Godot test automation involves creating a standardized tests directory, a GdUnit4-compatible runner, and a GitHub Actions workflow to execute tests on every push automatically.

What is the best way to add a smoke test gate for sprint QA handoff?▼

A smoke test gate for sprint handoff is added by seeding a critical-path smoke test checklist during the initial test directory scaffolding to ensure QA readiness before sprints begin.

Can I regenerate test directories and CI workflows without overwriting existing test files?▼

Yes, you can regenerate test directories and CI workflows idempotently without overwriting existing test artifacts, or use force-based regeneration behavior to repair test automation infrastructure.

Does the test scaffolding process require engine detection before creating files?▼

Yes, test scaffolding requires engine detection from project technical preferences and stops if the engine is not configured, gating user approval before creating any runner configuration or workflow files.

When should I initialize test automation infrastructure for my game repository?▼

You should initialize test automation infrastructure during the Technical Setup phase before sprints start, ensuring tests are runnable locally and automatically on GitHub Actions from the beginning.

Related Skills

Explore More Software Engineering Skills→
striderZAstriderZA
72

test-setup

Scaffold engine-specific test infrastructure and CI workflows for Godot, Unity, or Unreal.

Community
Intermediate
jmaglyjmagly
175

gate-evaluation

Validate phase-gate criteria and generate pass/fail gate reports.

Community
Advanced
RandallLiuXinRandallLiuXin
511

gdunit-driver

Run gdUnit4 tests for Godot projects and parse output into structured results.

Community
Intermediate
WindXRanWindXRan

test-setup

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

Community
Intermediate