gds-e2e-scaffold

Generates end-to-end testing infrastructure for Unity, Unreal, and Godot game projects.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/watchthelight/shatterfish --skill gds-e2e-scaffold-watchthelight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gds-e2e-scaffold
Source: https://github.com/watchthelight/shatterfish/tree/main/.claude/skills/gds-e2e-scaffold
Command: npx skills add https://github.com/watchthelight/shatterfish --skill gds-e2e-scaffold-watchthelight

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Setting up end-to-end tests for a game project requires significant boilerplate: test fixtures, scenario builders, input simulators, and async assertion utilities. Without this foundation, E2E tests become brittle and hard to maintain. This Skill scaffolds that entire infrastructure, tailored to the project's detected engine and architecture. ## Core Features & Use Cases - Engine Detection: Automatically detects Unity, Unreal, or Godot projects and generates engine-appropriate infrastructure code. - Infrastructure Generation: Creates GameE2ETestFixture, ScenarioBuilder, InputSimulator, and AsyncAssert components customized to the game's state manager, main scene, and input system. - Working Example Test: Generates a runnable example test that verifies the game loads, reaches ready state, and that input simulation works. - Use Case: A Unity developer with an existing game wants to start writing E2E tests. The Skill analyzes the project, generates the Tests/PlayMode/E2E directory with all infrastructure, an assembly definition, and a passing example test. ## Quick Start Ask the assistant to set up e2e testing infrastructure for your game project by saying "e2e scaffold" or "set up e2e testing".

Frequently Asked Questions about gds-e2e-scaffold

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

FAQPage Schema
How do I set up E2E testing for a Unity game?

Run the e2e scaffold workflow after initializing a test framework. It detects your engine, identifies the game state manager and main scene, then generates a Tests/PlayMode/E2E directory with a test fixture, scenario builder, input simulator, and async assertions.

What files does the E2E scaffold generate?

It generates an assembly definition, GameE2ETestFixture base class, ScenarioBuilder with a fluent API, InputSimulator matching your input system, AsyncAssert wait utilities, an example test, and a README with usage documentation.

Does the E2E scaffold support Unreal and Godot projects?

Yes, the workflow detects Unreal via .uproject files and Godot via project.godot, then generates equivalent infrastructure in C++ or GDScript under the appropriate test directories for each engine.

What prerequisites are required before running the E2E scaffold?

A test framework must already be initialized, the game must have an identifiable state manager class, and a functional main gameplay scene must exist. The workflow halts if existing E2E infrastructure is detected.

How does the InputSimulator handle Unity's New Input System?

When the New Input System is detected, it generates methods using InputState.Change and StateEvent.From for clicks, drags, and key presses. For Legacy Input, it generates a simpler version based on UI event triggering.