game-qa
Verify a game with evidence on its selected target runtime. Launch the actual build and check logs, real rendering, input and state changes, the core loop, designed outcomes, restart, target display modes, interface language, first-time onboarding, and whether the core fantasy is actually performed — without dressing subjective fun up as a certain verdict. Use for test a generated game, QA a game build, check whether the game is fully playable, verify the build. 游戏证据化质量验证。在选定的目标运行环境中启动实际构建，检查日志、真实画面、输入与状态变化、核心循环、设计要求的结果、重开、目标显示模式、界面语言、首次上手与核心幻想是否真正出现，不把主观趣味包装成确定性结论。用于测试生成游戏、检查游戏能否完整游玩等需求。
Profile →npx skills add worldwonderer/novel-to-game --skill game-qa --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 游戏质量验证 验证游戏能否可靠运行和完成，不给“好玩”伪造客观分数。 读取 [qa-contract.md](references/qa-contract.md) 定判据，读 [test-design-method.md](references/test-design-method.md) 定怎么设计这些检查。 产物语言由 `PRODUCT_BRIEF.md` 锁定；未锁定时跟随对话语言，不默认产出中文。 ## 执行 1. 先做 suite discovery：依次查 package/build manifest scripts、CI workflow 实际命令、测试 目录/文件、`BUILD_BRIEF.md` 声明的 runner，再对照 `qa/evidence/verify.log`。把结果写成 `suite | discovered from | files | runner | observed in verify | result`；发现 required suite 存在 却未被权威命令执行，报告 `ORPHANED_TEST_SUITE`，严重度 `major`。vendored/build output/ 明确 archived fixture 不算 suite，但例外必须写理由。 2. 从项目脚本和 `BUILD_BRIEF.md` 发现目标平台、`targetRuntime`、`testedRuntime` 与启动方式， 使用当前环境中适合该运行时的测试能力；网页才使用浏览器测试。独立运行 brief 声明的 权威 verify，记录实际 command、exit code、duration、environment 和 source commit；不能只 接受实现方贴出的绿色摘要。提取不变量以 `BUILD_BRIEF.md` 回写后的「# 范围」与「最终范围对照」为依据；发现 brief 范围与代码 不一致（如 brief 三战、代码六战）先记 `major` 要求回写再验。同时逐字核对 `PRODUCT_BRIEF.md`、`ART_DIRECTION.md`、`VISUAL_TARGETS.md`、`BUILD_BRIEF.md` 的 `targetFinish`；任一缺失或不一致即 `FAIL`，不由 QA 猜一个等级。 3. 审计 `qa/verification.json`：环境、verify、suites、completeRun、checkpoints 必须属于同一 source commit。复跑一条 `clean start → 核心动作 → 设计结果 → restart`，逐步核对 checkpoint； 同时核对 registry 的 discovered / registered / excluded /
- 执行
- 输出
What does the game-qa skill do?
Verify a game with evidence on its selected target runtime. Launch the actual build and check logs, real rendering, input and state changes, the core loop, designed outcomes, restart, target display modes, interface language, first-time onboarding, and whether the core fantasy is actually performed — without dressing subjective fun up as a certain verdict. Use for test a generated game, QA a game build, check whether the game is fully playable, verify the build. 游戏证据化质量验证。在选定的目标运行环境中启动实际构建，检查日志、真实画面、输入与状态变化、核心循环、设计要求的结果、重开、目标显示模式、界面语言、首次上手与核心幻想是否真正出现，不把主观趣味包装成确定性结论。用于测试生成游戏、检查游戏能否完整游玩等需求。
How do I install it?
Run `npx skills add worldwonderer/novel-to-game --skill game-qa --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From worldwonderer/novel-to-game, a repository with 555 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.