skills.rest
FrancisVarga
FrancisVargaCOMMUNITY
Explore all skills by this author →
GitHub

smoke-check

Execute automated and manual smoke tests and generate a PASS/FAIL report.

Updated May 13, 2026
Search Tags:#game development#test automation#report generation#smoke testing#qa gate#coverage validation#platform checks
One-click install
npx skills add https://github.com/FrancisVarga/the-dream-machine --skill smoke-check-francisvarga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/FrancisVarga/the-dream-machine/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/FrancisVarga/the-dream-machine --skill smoke-check-francisvarga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken game builds from reaching QA by running an automated smoke test workflow and verifying core functionality before hand-off.

Core Features & Use Cases

  • Automated test execution by engine: Detects the project engine and runs the appropriate headless or artifact-based test approach, then extracts pass/fail details.
  • Coverage gap detection: Compares sprint story scope against unit/integration test evidence to flag missing coverage without blocking everything automatically.
  • Interactive manual smoke verification: Runs structured, batched manual checks (and optional platform-specific checks) with user confirmation, then generates a PASS/FAIL gate report.

Quick Start

Run smoke-check in sprint mode with the option for a specific target platform by saying: /smoke-check sprint --platform pc.

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 to gate a game build before QA hand-off?▼

Automated smoke testing for game builds detects the project engine and runs appropriate headless or artifact-based tests to extract pass/fail details. This prevents broken game builds from reaching QA by verifying core functionality before hand-off.

How do I detect missing test coverage for sprint stories in game development?▼

Coverage validation for sprint stories compares sprint story scope against unit and integration test evidence to flag gaps. It assigns MISSING, EXPECTED, or covered statuses to identify missing coverage without automatically blocking the entire build.

Can I execute platform-specific manual smoke checks for game builds?▼

Platform checks for game builds execute structured, batched manual verifications with optional platform-specific configurations. Users provide interactive confirmations during the smoke test, which are then compiled into a gate report without auto-writing files.

Does the smoke test report auto-write to the project directory?▼

No, the smoke test report does not auto-write to your directory. Interactive user confirmations are gated into a smoke-[date].md report file, requiring manual approval before the PASS/FAIL validation results are saved.

What is the best way to verify game build readiness across multiple supported engines?▼

Verifying game build readiness across engines requires environment detection of test setup and engine preferences. The system identifies the engine and runs the appropriate headless or artifact-based test approach to extract pass/fail details for regression gating.

Related Skills

Explore More Software Engineering Skills→
striderZAstriderZA
72

smoke-check

Run automated smoke tests and generate a PASS/FAIL QA readiness report.

Community
Advanced
brand6brand6

smoke-check

Run automated smoke tests and generate PASS/FAIL reports for QA readiness.

Community
Advanced
Euraika-LabsEuraika-Labs
14

smoke-check

Run critical path smoke tests and produce a PASS/FAIL report.

Official
Advanced
solace-illsolace-ill

smoke-check

Run automated test suites and produce PASS/FAIL reports for QA hand-off.

Community
Advanced