test-setup

Scaffold engine-specific test infrastructure and GitHub Actions CI/CD workflows.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill test-setup-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-setup
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/test-setup
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill test-setup-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually setting up automated testing infrastructure and CI/CD pipelines for game engines is time-consuming, inconsistent, and often delayed until late in development, leading to expensive bug fixes and rework when issues are discovered after implementation is complete.

Core Features & Use Cases

  • Multi-Engine Support: Auto-detects configured game engines (Godot, Unity, Unreal Engine, Babylon.js) and generates engine-specific test runner configurations.
  • Standardized Test Layout: Creates a consistent test directory structure with unit, integration, smoke, and evidence folders to align team testing practices.
  • CI/CD Integration: Automatically sets up GitHub Actions workflows to run tests on every push to main and pull request, blocking merges on test failures.
  • Use Case: For a Babylon.js racing game project, this skill can scaffold the full Vitest test setup and CI pipeline in 5 minutes during the technical setup phase, before any game code is written.

Quick Start

Invoke the test-setup skill during your project's technical setup phase to automatically generate the complete test infrastructure and CI workflow for your configured game 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 automated testing for a game engine project?

Automated testing for game engine projects is set up by scaffolding standardized test directory structures and generating engine-specific test runner configurations for Godot, Unity, Unreal Engine, or Babylon.js. This eliminates manual setup delays and inconsistencies.

Can I generate GitHub Actions workflows to run game tests on every push?

Yes, GitHub Actions workflows can be automatically generated to execute tests on every code push and pull request. This CI/CD integration blocks merges on test failures, ensuring code quality throughout development.

Does this test setup work with Unity and Unreal Engine?

Yes, this test setup works with Unity and Unreal Engine, as well as Godot and Babylon.js. It auto-detects configured game engines and generates the appropriate engine-specific test runner configurations.

When should I scaffold test infrastructure for my game development project?

You should scaffold test infrastructure during the technical setup phase, before any game code is written. Satisfying pre-implementation test framework requirements early reduces costly late-stage rework.

What is the best way to standardize test directories for a Babylon.js game?

The best way to standardize test directories for a Babylon.js game is to scaffold the complete test infrastructure and CI pipeline automatically. This generates a consistent layout, such as a full Vitest setup, in minutes.