About test-setup
test-setup is a project setup skill that detects the configured engine and scaffolds automated testing infrastructure. It creates a test directory layout and CI workflow, while requiring approval before file creation and avoiding overwrites.
Key features
- 01Detects the configured engine
- 02Generates test runner configuration
- 03Creates a standard tests/ layout
- 04Adds a GitHub Actions test workflow
- 05Seeds a smoke test
Use cases
- 01Set up testing before implementation begins
- 02Add missing test infrastructure to an existing project
- 03Run tests automatically on each push
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/test-setupin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
references/1-detect.md2-plan.md3-directories.md4-ci.md5-smoke-seed.md6-summary.mdDetails
From the project README!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Test Setup
This skill scaffolds the automated testing infrastructure for the project. It detects the configured engine, generates the appropriate test runner configuration, creates the standard directory layout, and wires up CI/CD so tests run on every push.
Run this once during the Technical Setup phase, before any implementation begins. A test framework installed at sprint start costs 30 minutes. A test framework installed at sprint four costs 3 sprints.
Output: tests/ directory structure + .github/workflows/tests.yml
Phase 1: Detect Engine and Existing State
Read references/1-detect.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 2: Present Plan
Read references/2-plan.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 3: Create Directory Structure
Read references/3-directories.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 4: Create CI/CD Workflow
Read references/4-ci.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 5: Create Smoke Test Seed
Read references/5-smoke-seed.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Phase 6: Post-Setup Summary
Read references/6-summary.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.
Collaborative Protocol
- Never overwrite existing test files — only create files that are missing. If a test runner file exists, leave it as-is.
- Always ask before creating files — Phase 2 requires explicit approval.
- Engine detection is non-negotiable — if the engine is not configured,
stop and redirect to
/setup-engine. Do not guess. forceflag skips the "already exists" early-exit but never overwrites. It means "create any missing files even if the directory already exists."- For Unity CI, note that the
UNITY_LICENSEsecret must be configured manually. Do not attempt to automate license management.