smoke-check

Execute automated test suites and collect manual smoke-check confirmations for build readiness.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/dnkrow/skill --skill smoke-check-dnkrow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/dnkrow/skill/tree/main/claude-global/smoke-check
Command: npx skills add https://github.com/dnkrow/skill --skill smoke-check-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Smoke-checks prevent broken builds from reaching manual QA by running automated tests and validating core functionality before hand-off.

Core Features & Use Cases

  • Automated test execution by detected engine: Runs the appropriate test runner (e.g., Godot via gdunit4 runner) and summarizes passing/failing results.
  • Coverage gap detection for story scope: Scans expected test evidence per story and flags missing coverage as advisory gaps (not immediate FAIL blockers).
  • Interactive manual smoke batches: Uses guided questions to verify key gameplay and regression checks (with optional platform-specific batches).

Example: After a sprint implements new features, run smoke-check to confirm the automated suite is green and that core stability, the primary mechanic, and save/load behave correctly before QA starts.

Quick Start

Run the full gate for your sprint by invoking /smoke-check sprint with the appropriate platform flag if you need platform-specific checks.

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 gate to verify build readiness before QA handoff?

A smoke test gate verifies build readiness by executing automated test suites, checking story test coverage, and collecting manual confirmations. It generates a PASS/FAIL verdict and a date-stamped report file for sprint hand-offs.

Can I perform platform-specific smoke testing for PC, console, and mobile builds?

Yes, platform-specific smoke testing is supported for pc, console, and mobile builds. The gate runs interactive manual smoke batches with guided questions to verify key gameplay and regression checks per platform.

What happens if my game engine test infrastructure is missing during a smoke check?

When test infrastructure is missing during a smoke check, the gate handles it as NOT RUN with warnings rather than an automatic failure. This prevents false negatives when automated test suites cannot execute.

How does story test coverage gap detection work during sprint hand-offs?

Coverage gap detection scans expected test evidence per story and flags missing coverage as advisory gaps. These gaps are reported as warnings rather than immediate FAIL blockers, ensuring builds proceed while highlighting untested areas.

Does smoke testing work with Godot game engine test runners?

Yes, smoke testing detects the game engine and runs the appropriate test runner, such as gdunit4 for Godot. It summarizes passing and failing test results to determine the final build readiness verdict.

What's the best way to generate a deterministic PASS/FAIL report for QA handoff?

The best way to generate a deterministic QA report is to run an automated smoke gate that produces a date-stamped PASS/FAIL verdict file. This report combines automated test results, coverage scans, and manual confirmations.