smoke-check

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

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill smoke-check-brand6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/brand6/Claude-Code-Game-Studios-zh-auto/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/brand6/Claude-Code-Game-Studios-zh-auto --skill smoke-check-brand6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before handing off to QA, enforce a gate by executing key-path smoke tests. This skill runs automated test suites to verify core functions and generates PASS/FAIL reports to ensure only healthy builds progress to QA.

Core Features & Use Cases

  • Orchestrates automated smoke tests across sprint-ready builds.
  • Generates PASS/FAIL reports and highlights missing coverage or flaky tests.
  • Outputs reports to production/qa/smoke-[date].md and supports platform variants.

Quick Start

Run smoke-check for the current sprint to validate core paths and generate a pass/fail report.

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 before handing off a sprint build to QA?

To run automated smoke tests before a QA handoff, execute a test suite against sprint-bound builds to verify core paths and generate PASS/FAIL reports ensuring only healthy builds progress.

What is a QA readiness gate and how does it handle platform variants?

A QA readiness gate enforces smoke testing before handoff, applying automated test execution across platform variants like pc, console, mobile, or all, reporting PASS/FAIL status with an optional platform breakdown.

Can I generate standardized QA reports for CI automated smoke tests?

Yes, you can generate standardized QA reports for CI smoke tests by parsing test results and outputting a production/qa/smoke-[date].md report that highlights missing coverage or flaky tests.

Does the smoke test gate support builds for both mobile and console platforms?

Yes, the smoke test gate supports builds for mobile and console platforms by applying automated test execution to specified variants and reporting a platform-specific PASS/FAIL breakdown.

Why do I need to parse test results for sprint-bound builds?

Parsing test results for sprint-bound builds is required to identify missing coverage or flaky tests, generate a standardized QA report, and enforce the gate by determining the final PASS/FAIL status.