smoke-check

Name: smoke-check
Availability: InStock
Author: easonlao

Run automated tests and interactive smoke checks into a PASS/FAIL report.

Updated Apr 25, 2026

Search Tags:#test coverage #godot #ci #release gating #smoke testing #qa hand-off #platform smoke checks

Ready to run

npx skills add https://github.com/easonlao/jiazi-game --skill smoke-check-easonlao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/easonlao/jiazi-game --skill smoke-check-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or incomplete builds from reaching manual QA by running an automated critical-path test suite and required smoke checks, then producing a clear PASS/FAIL gate result.

Core Features & Use Cases

Automated test execution with engine-aware runners: Detects the project engine, runs the appropriate headless test command, and records pass/fail counts and failures.
Coverage gap assessment: Compares sprint/QA-plan story scope against available unit/integration/evidence files and flags missing coverage without turning it into a hard FAIL by itself.
Manual smoke verification batching: Uses interactive question prompts to confirm core stability, sprint mechanic/regressions, and (when not in quick mode) save/performance checks, then composes a final verdict.

Quick Start

Run /smoke-check sprint --platform pc to gate the current sprint build with both automated tests and PC-relevant manual smoke checks.

Frequently Asked Questions about smoke-check

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

FAQPage Schema

How do I gate a build for QA hand-off with automated smoke testing?▼

To gate a build for QA hand-off, the system runs automated tests and interactive smoke verification across sprint scope, producing a PASS/FAIL report and an approval-gated artifact at production/qa/smoke-[date].md.

How does smoke check coverage gaps before manual QA begins?▼

Smoke check compares sprint or QA-plan story scope against available unit, integration, and evidence files to flag missing coverage. This coverage gap assessment prevents incomplete builds from advancing without causing a hard FAIL by itself.

Does the smoke test readiness gate support platform-specific checks for PC builds?▼

Yes, the readiness gate supports optional platform-specific batches. You can run /smoke-check sprint --platform pc to execute automated tests and PC-relevant manual smoke checks for your current sprint build.

Can I use automated test execution with engine-aware runners for Godot projects?▼

Yes, the engine-aware runners detect the project engine, such as Godot, and run the appropriate headless test command. This automatically records pass/fail counts and failures to validate critical-path stability.

How do I verify sprint regressions and save performance checks before QA?▼

Interactive question prompts confirm core stability, sprint mechanic regressions, and save or performance checks. When not in quick mode, these manual smoke verification batches compose a final readiness verdict before QA hand-off.