smoke-check

Execute automated test suites and produce a PASS/FAIL smoke report.

Updated Apr 8, 2026
One-click install
npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill smoke-check-hechaoyannet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/HechaoYannet/3kingdom-unity/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/HechaoYannet/3kingdom-unity --skill smoke-check-hechaoyannet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Smoke Check skill acts as the gate between "implementation done" and "ready for QA hand-off" by running the automated test suite, verifying core functionality, and producing a PASS/FAIL report, ensuring only solid builds advance to QA.

Core Features & Use Cases

  • Runs the project's automated tests and validates test results across sprint scope and platform variants.
  • Analyzes test coverage, checks for regressions, and outputs a standardized smoke report suitable for hand-off.
  • Generates a production-ready smoke report file and supports both automated and manual smoke batches for QA readiness.

Quick Start

Run the smoke-check sprint to gate the build for QA.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I automate a build verification smoke check before QA hand-off?

A smoke check for QA readiness executes the automated test suite across sprint scope and platform variants, producing a consolidated PASS/FAIL report. It validates core functionality and checks for regressions to ensure only solid builds advance to QA.

Can I generate platform-specific test results when running automated smoke checks?

Yes, automated smoke checks generate a consolidated Smoke Check Report alongside optional platform-specific results. This validates test coverage across platform variants and optional manual batches to guide stakeholder communication and QA hand-off.

What is the best way to gate builds using automated testing and regression checks?

Gate builds by executing the automated test suite to analyze test coverage and check for regressions. This approach identifies build readiness through phased verification and AskUserQuestion, producing a standardized smoke report before QA hand-off.

Does the smoke check process support both automated and manual test batches?

Yes, the smoke check process supports both automated and manual smoke batches for QA readiness. It uses phases and AskUserQuestion for verification, coordinating sprint scope, QA plans, and platform variants to produce a consolidated Smoke Check Report.

Why do I need to run automated tests and check for regressions before QA hand-off?

Running automated tests and checking for regressions before QA hand-off ensures only solid builds advance. It acts as a gate between implementation and QA readiness, verifying core functionality and producing a standardized smoke report suitable for stakeholder communication.