smoke-check

Runs automated tests and manual smoke checks to produce a PASS/FAIL QA gate report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents broken game builds from being handed to QA by enforcing a structured smoke test gate between implementation and manual QA, combining automated test results, coverage analysis, and developer-verified manual checks into a single verdict. ## Core Features & Use Cases - Engine-aware test execution: Detects Godot, Unity, or Unreal from project configuration and runs or locates the appropriate test results, treating unavailable runners as NOT RUN rather than automatic failures. - Coverage gap analysis: Maps sprint stories to test files and flags Logic/Integration stories with MISSING test evidence before they can be closed. - Batched manual verification: Uses multi-select prompts for core stability, sprint regression, and data integrity checks, with optional PC, console, and mobile platform batches. - Use Case: After finishing a sprint's stories in a Godot project, run the smoke check to execute the GDUnit4 suite, verify the new combat mechanic manually, and receive a PASS WITH WARNINGS report listing two stories still missing test files. ## Quick Start Ask the AI to run the smoke check gate for the current sprint before QA hand-off and report the verdict.

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?

Run the smoke check after a sprint's stories are implemented. It detects your engine, runs or locates automated tests, verifies critical paths through batched manual check prompts, and produces a PASS/FAIL report saved to production/qa/.

How do I check test coverage for sprint stories?

The coverage phase maps each sprint story to files in tests/unit/ and tests/integration/ by system slug, then labels stories COVERED, MANUAL, MISSING, or EXPECTED. MISSING entries are advisory gaps that must be resolved before stories can be marked complete.

Does the smoke check work with Unity or Unreal projects?

Yes, it reads the engine from .ai-game-studio/project.json. Unity and Unreal tests usually cannot run headlessly, so it looks for recent test result artifacts or automation logs and asks you to confirm status manually.

What happens if automated tests cannot run in my environment?

Tests that cannot execute are recorded as NOT RUN, not FAIL. The verdict becomes PASS WITH WARNINGS until you manually confirm results from your IDE or CI pipeline, since unconfirmed NOT RUN never blocks QA hand-off.

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 batch, rerunning only core stability and regression checks to confirm the fix.