smoke-check

Runs automated tests and manual smoke checks to gate builds before QA hand-off.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill smoke-check-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/smoke-check
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill smoke-check-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handing a broken build to QA wastes tester time and demoralizes the team. This Skill enforces a critical-path smoke test gate between implementation and QA hand-off, producing a clear PASS/FAIL verdict so only verified builds move forward. ## Core Features & Use Cases - Automated Test Execution: Detects the game engine (Godot, Unity, Unreal) and runs or verifies the test suite, parsing pass/fail counts and failing test names. - Coverage Gap Analysis: Maps sprint stories to test files and flags Logic/Integration stories missing test evidence before they can be marked complete. - Interactive Manual Verification: Batch-verifies core stability, sprint regressions, save/load integrity, and platform-specific checks (PC, console, mobile) through structured multi-select prompts. - Use Case: After finishing a sprint's stories, run the smoke check to execute the test suite, confirm the main menu and core mechanic still work, and generate a dated report in production/qa/ with a PASS, PASS WITH WARNINGS, or FAIL verdict. ## Quick Start Ask the AI to run the smoke check gate for the current sprint before handing the build off to QA.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I run a smoke test before QA hand-off?

Invoke the smoke-check skill after sprint stories are implemented. It detects your engine, runs the automated test suite, batch-verifies core stability and sprint changes with you, then writes a PASS/FAIL report to production/qa/smoke-[date].md.

What happens if automated tests cannot run in my environment?

Tests that cannot execute are recorded as NOT RUN, not FAIL. You confirm results manually from your IDE or CI pipeline, and unconfirmed NOT RUN contributes to a PASS WITH WARNINGS verdict rather than blocking the build.

Does smoke-check support Godot, Unity, and Unreal Engine?

Yes. It reads the engine from .ai-game-studio/project.json and selects the appropriate test command: GDUnit4 headless runner for Godot, test result artifacts for Unity, and automation logs for Unreal Engine.

Can I run platform-specific smoke checks for console or mobile?

Yes. Pass --platform pc, console, mobile, or all to add targeted batches covering gamepad input, TV safe zones, touch controls, orientation changes, and thermal behavior, with a per-platform verdict table in the report.

What causes a smoke check to fail?

The verdict is FAIL if the automated suite reports failures, any core stability check fails, or the primary sprint mechanic or a regression check fails. Missing test evidence alone produces PASS WITH WARNINGS, not FAIL.

When should I use the quick argument instead of a full smoke check?

Use quick for rapid re-checks after fixing a specific failure. It skips the coverage scan and the data integrity/performance batch, so it is faster but does not replace a full sprint smoke check before QA hand-off.