smoke-check

A smoke test gate runs critical path automated tests, verifies story-to-test coverage, and coordinates manual verification batches to produce a PASS or FAIL report for your game development build.

Story-to-test coverage scans your repository to map automated tests to specific user stories, marking coverage status per story. It highlights missing test evidence, which blocks story completion and fails the smoke check gate.

The smoke test gate detects your test framework, CI presence, and engine configuration through docs/studio/technical-preferences.md to select appropriate test commands. It requires repository access to tests and QA plans to execute properly.

To conduct manual verification batches during a sprint smoke check, the skill runs up to three batches plus optional platform-specific checks, collects your user responses, and assembles a detailed PASS, PASS WITH WARNINGS, or FAIL verdict.

When automated test runners are unavailable during a smoke test, the skill inspects existing test results, parses pass/fail counts, and records NOT RUN warnings for the missing tests in the final smoke check report.

To generate a smoke check report for all platforms, run the sprint command with the all platform flag. The skill asks for explicit approval before writing the production/qa/smoke-[date].md report file.