Test Setup

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Test Setup" for me. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. The skill itself scaffolds a game project's automated testing infrastructure, once, before the first sprint: it detects the configured engine and any existing test state, presents a plan that requires explicit approval (its Phase 2), then creates the engine's standard test directory layout and test-runner configuration, the CI workflow file .github/workflows/tests.yml (GitHub Actions, per-engine: GdUnit4 for Godot, game-ci for Unity, a self-hosted Windows runner for Unreal), and a smoke-test seed, following its six phase files under references/ in turn. It never overwrites existing test files (the optional 'force' argument only creates files that are missing), stops and redirects to /setup-engine when no engine is configured, and notes that for Unity CI the UNITY_LICENSE secret must be configured manually by the user in their own repository: the skill does not handle license management or collect any credential. The CI workflow it writes runs the project's tests on GitHub's infrastructure at use time (on push), which is a file it creates in the user's own repo, not a service the skill connects to during the install. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/test-setup/ folder at the pinned commit: 7 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/test-setup/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 7d420f14829ba4062dcaf354a91808e41523c091516160593bac048533679973 - references/1-detect.md: SHA-256 88e37a991c459ec5021a6be8657e5ca0ef6909354c407cd00364eb36c17c31c2 - references/2-plan.md: SHA-256 c815ab098204cdf75159bc544100b7538f20500204f60590a3544ac6969932b4 - references/3-directories.md: SHA-256 87d07a2a7a8fd4eeb642a6d310057f6a315e2d534cdab2c4739de86c57468be1 - references/4-ci.md: SHA-256 1897b67d5b21a5274e83758a356837076e5bd6fd2886ad05dbb96eccb1a45245 - references/5-smoke-seed.md: SHA-256 c2c4dabcf16bca70fa3d4170b5fbb6ea9ae92dae4567a23fc0066025f5c9ba6e - references/6-summary.md: SHA-256 4b614ab4edcc1e9b90f7b8429b3498e17dd59055f592c7565c3689484f18298a If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 7 files: SKILL.md plus 6 phase files under references/ (1-detect, 2-plan, 3-directories, 4-ci, 5-smoke-seed, 6-summary) that the SKILL.md reads and follows in turn. Nothing in the folder is a program. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is scaffolded or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (outside this skill's folder, absent standalone), and checks a Unity manifest with a local grep. Inside the template it works on my project's own files, locally. - At use time it creates real project files, only after its plan phase gets explicit approval: the engine's tests/ directory layout and runner configuration, a smoke-test seed, and the GitHub Actions workflow .github/workflows/tests.yml in my own repository. It never overwrites existing test files; for Unity CI I must configure the UNITY_LICENSE secret in my repo myself, the skill never asks for or handles it. - Do not scaffold anything, do not run any template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole test-setup folder into the agent's skills directory, in a folder named exactly "test-setup", keeping its 7 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: test-setup), the 7 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone, and what it does inside the template). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.