test-setup

Create engine-specific test directories and GitHub Actions workflow files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often lack reliable automated test structure and continuous verification, causing regressions to slip in until late manual QA.

Core Features & Use Cases

  • Engine-aware test scaffolding: Detects the configured engine and prepares the correct test runner artifacts and directory layout.
  • Standard test organization: Creates unit, integration, smoke, and evidence areas so teams can consistently add coverage over time.
  • CI/CD wiring: Generates a GitHub Actions workflow that runs tests on push and pull requests and captures results for review.

Use case example: Before the first sprint that adds new gameplay logic in a Godot project, run this skill to create the tests/ structure and set up CI so each change is validated automatically.

Quick Start

Run the test-setup skill to scaffold the engine-specific tests directories and GitHub Actions workflow for your repository.

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 tests and CI for a Godot project?

Test scaffolding creates a standardized tests/ directory layout organized into unit, integration, smoke, and evidence areas, ensuring teams can consistently add coverage over time to prevent regressions from slipping in until late manual QA.

Can I generate a GitHub Actions workflow for test scaffolding without overwriting existing files?

Engine-aware test scaffolding detects the configured engine from technical preferences and prepares the correct test runner artifacts, configuration files, and directory layout specific to that engine.

What is the best way to organize unit, integration, and smoke tests for continuous integration?

When you run the test scaffolding, it detects your configured engine, creates missing tests directories and runner/config files, and generates the .github/workflows/tests.yml workflow without overwriting existing files.

Does GdUnit4 test scaffolding work with GitHub Actions to prevent regressions?

The scaffolding is designed for technical setup workflows where the repository needs a standardized tests/ layout and engine-specific runner, applying to game or engine projects that lack reliable automated test structure.