smoke-check

Run automated test suites and generate PASS/FAIL smoke reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill smoke-check-thilthpc01208
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/thilthpc01208/Codex-Game-Studios/tree/main/.codex/skills/smoke-check
Command: npx skills add https://github.com/thilthpc01208/Codex-Game-Studios --skill smoke-check-thilthpc01208

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the gate between implementation completion and QA hand-off by running the automated test suite and producing a PASS/FAIL report.

Core Features & Use Cases

  • Runs the project’s automated tests and reports PASS/FAIL status to prevent QA hand-off on broken builds.
  • Supports sprint and quick modes, and optional platform scopes to tailor checks for pc, console, or mobile builds.

Quick Start

Start a smoke check for the current sprint to validate the build before QA.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I automate a build gate for smoke tests before QA hand-off?

Automating a build gate for smoke tests involves running the automated test suite after sprint implementation to produce a PASS/FAIL report, preventing manual QA from starting on a broken build.

Can I run targeted automated smoke tests for specific platforms like console or mobile?

Yes, you can run targeted automated smoke tests for specific builds by applying optional platform scopes such as pc, console, or mobile to tailor the environment checks and test execution.

What is the difference between sprint and quick modes when running an automated test suite?

Sprint and quick modes tailor the automated test suite execution; sprint mode validates the full sprint implementation before QA, while quick mode provides a faster validation pass for the build gate.

How do I generate a standardized QA report after running automated tests?

To generate a standardized QA report after running automated tests, the test runner parses the execution results and outputs a production/qa/smoke-[date].md file detailing the PASS/FAIL status.

Does the automated smoke test runner handle environment checks before executing the test suite?

Yes, the automated smoke test runner orchestrates environment checks before executing the test suite, ensuring the build environment is correctly configured prior to validating the implementation for QA hand-off.