smoke-check

Name: smoke-check
Availability: InStock
Author: scomofo

Execute automated tests and guided smoke checks, then generate a PASS/FAIL report.

Updated Mar 28, 2026

Search Tags:#test coverage #godot #automated tests #smoke testing #qa gating #platform validation #regression checks

Ready to run

npx skills add https://github.com/scomofo/dragon-forge --skill smoke-check-scomofo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/smoke-check
Command: npx skills add https://github.com/scomofo/dragon-forge --skill smoke-check-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Smoke-check prevents broken builds from reaching manual QA by running automated tests and targeted smoke validations, then producing a clear PASS/FAIL gate report.

Core Features & Use Cases

Automated test gate: Runs the configured Godot/engine test suite and extracts pass/fail and failing test names for fast triage.
Coverage gap detection: Compares sprint/QA plan story scope against expected test coverage and flags missing evidence as advisory gaps.
Human-in-the-loop smoke verification: Uses guided checks to confirm core stability, sprint regression, and (optionally) save/performance sanity before declaring readiness.
Use Case: After implementing hatchery sprint stories, run this skill to confirm the build is stable for QA and capture exactly what failed (including platform-specific issues).

Quick Start

Run smoke-check for the current sprint on your target platform by executing: /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 automated smoke tests to gate a Godot game build before QA hand-off?▼

Run automated smoke tests to gate a Godot build by executing the test suite and guided checks, which generates a PASS/FAIL report confirming core stability and sprint regression readiness.

What is qa gating for post-sprint validation and how does it work?▼

QA gating for post-sprint validation is the process of running automated tests and coverage scans to block broken builds from reaching manual QA, producing an auditable PASS/FAIL result with missing-story reporting.

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

Yes, you can perform platform-specific smoke testing across PC, console, and mobile by targeting your desired platform during execution, allowing validation of platform-specific regressions before QA hand-off.

Do I need existing automated tests to execute a smoke check?▼

Yes, you need existing automated tests and engine configuration present in your project to execute a smoke check, as the skill parses test runner outputs and performs coverage gap detection against expected story scope.

How do I detect test coverage gaps for my sprint QA plan?▼

Detect test coverage gaps by comparing sprint or QA plan story scope against expected test evidence, which flags missing verification inputs as advisory gaps within the generated production smoke output report.

What is the best way to capture manual verification inputs during a smoke check?▼

Capture manual verification inputs by using the guided human-in-the-loop checks to confirm stability, then recording those manual inputs directly into the final auditable QA smoke output report.