smoke-check

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.

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.

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.

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.

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.

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.