Smoke Check

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. At use time this skill RUNS the project's own automated test suite on your machine (engine and test commands with long timeouts, disclosed in full below) — running those tests is its job; nothing of the sort happens during installation. Install "Smoke Check" for me. The skill itself is the gate between "implementation done" and "ready for QA hand-off". It detects the test setup (game test files at the engine's test root, CI workflows, the engine from project.yaml, the smoke test list and the current QA plan), then actually runs the automated test suite: the project's own commands.test from project.yaml when set, otherwise per-engine defaults — Godot 4 headless via gdUnit4 after a headless import, Unity headlessly in Edit Mode and then Play Mode as a second run, Unreal with a build first — under 900 or 1800 second timeouts, where a timeout is a gate failure, never a pass, and zero tests found is NOT ASSESSED, never a pass. It then checks test coverage against the sprint's stories (skipped in quick mode), batch-verifies the critical paths with the developer through AskUserQuestion (the developer confirms manually; the skill runs no game itself), and generates the report with verdict PASS, PASS WITH WARNINGS, NOT ASSESSED or FAIL, optionally per platform with --platform pc, console, mobile or all. In Phase 6 it asks "May I write this smoke check report to production/qa/smoke-[date].md?" and writes only on approval; a FAIL blocks QA hand-off by default (blocking unless testing.strict.config resolves advisory). It never auto-fixes failures and never edits source or test files. It resolves automation, workflow, qa.level and testing.strict by running the template's hooks/yaml-helper.sh, outside this skill's folder, and follows its six phase files under references/ in turn. Its frontmatter pins model: sonnet. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/smoke-check/ 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/smoke-check/ 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 8531f6d673bf35704b2a0676594e3ab4d6af0153fe772ab590479247fddee6d0 - references/1-detect-setup.md: SHA-256 07af6a1dc13f17fddb6f1877e578969471ffa37e3e5b1845334ca216a36fdff3 - references/2-run-tests.md: SHA-256 93981f1b4aadeff6d3c8db199de990972e7a7d0540313e3cad4c74aaf52c9f62 - references/3-coverage.md: SHA-256 34cee3af8199169ed5771a889174c96f955ed3a56cf26fd56077fada46d62224 - references/4-manual-checks.md: SHA-256 08d9d33dd0441f00346500e00bbea206c21239d83190cc6edbb5d986f9721d07 - references/5-report.md: SHA-256 f819079544bfd59504d79d1e6a6607aaf98f7476cef0a91e15eb6cf1f73adabb - references/6-write-gate.md: SHA-256 35510aaea59e83332a5eccc98a417afed5327114a6180fe62f2b7344cd716192 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-setup, 2-run-tests, 3-coverage, 4-manual-checks, 5-report, 6-write-gate). Nothing in the folder is a program; the phase files are instructions the skill reads and follows at use time — the commands it runs at use time are the project's own test and engine commands, which live outside this folder. - 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 audited, read or modified. - Integrated-system reality, from the files: at use time the skill runs the template's hooks/yaml-helper.sh to resolve automation, workflow, qa.level and testing.strict, follows .claude/docs/automation-modes.md and the template's directory structure, reads project.yaml, the sprint stories and the QA files under production/qa/, and runs the project's test command and engine executables locally (Godot headless, the Unity editor in batch mode, Unreal builds) — the hook, the docs and the project's own test setup live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time it executes the project's automated tests on my own machine (disclosed above and in the prerequisites) and writes only the smoke report, production/qa/smoke-[date].md, only after its Phase 6 ask; it never auto-fixes a failure and never edits source code or test files. No third-party service, account or credential is named in the files. - Do not run any test, engine command, template hook or script, 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 smoke-check folder into the agent's skills directory, in a folder named exactly "smoke-check", keeping its 7 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: smoke-check), 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 (it resolves its gate settings through the template's yaml-helper hook and needs the project's own test setup), and that at use time it actually runs my automated test suite locally, blocks QA hand-off on a FAIL by default, and writes its report only after asking). 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.