test-setup

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

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill test-setup-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/dnkrow/skill/tree/main/claude-global/test-setup
Command: npx skills add https://github.com/dnkrow/skill --skill test-setup-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the friction of setting up a consistent automated test framework and continuous integration pipeline by scaffolding the required directories, engine-specific runners, and a GitHub Actions workflow.

Core Features & Use Cases

  • Engine-aware test scaffolding: Detects the configured engine from technical preferences and generates the correct test runner and placeholders for that engine.
  • CI/CD workflow wiring: Creates a .github/workflows/tests.yml workflow to run the right tests on pushes and pull requests.
  • Non-destructive initialization: Creates only missing files while preserving any existing test infrastructure and respecting the force argument for regeneration without overwriting.

Quick Start

Run the skill to scaffold your test directories, engine-specific runner files, and the GitHub Actions workflow by executing: /test-setup.

Frequently Asked Questions about test-setup

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

FAQPage Schema
How do I scaffold unit and integration tests for my Godot, Unity, or Unreal project?

Scaffold engine-aware automated testing infrastructure by generating standardized test directories, engine-specific runners, and placeholder files configured for Godot, Unity, or Unreal environments.

Can I set up a GitHub Actions workflow to run tests automatically on pull requests?

Yes, continuous integration workflow wiring creates a .github/workflows/tests.yml file to run engine-specific unit, integration, and smoke tests automatically on pushes and pull requests.

What is the best way to initialize a CI/CD pipeline without overwriting existing test infrastructure?

Non-destructive initialization creates only missing test files and directories while preserving existing test infrastructure, ensuring current runners remain safe during pipeline scaffolding.

Does test scaffolding require a specific configuration file to detect the engine?

Yes, engine detection requires reading the configured engine setting from the .claude/docs/technical-preferences.md file to generate the correct engine-specific test runner.

How do I regenerate test directories and workflow files if my project setup changes?

Regenerate test directories and the GitHub Actions workflow by using a force flag, which overrides non-destructive initialization to rebuild the testing infrastructure.

Why does the test scaffolding process require approval before generating files?

The scaffolding process refuses to proceed without approval to ensure you explicitly authorize the creation of test directories, runner files, and smoke test seeds in your repository.