smoke-check

Run engine-specific automated smoke tests and record PASS/FAIL verdicts.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill smoke-check-imclab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill smoke-check-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Smoke-checking catches broken builds early by running the critical path test suite and required manual verifications before QA spends time validating a bad release.

Core Features & Use Cases

  • Automated critical path tests: Detects missing test setup, selects the right test runner by engine, runs the suite when possible, and captures PASS/FAIL plus failing test names.
  • Coverage and evidence awareness: Checks story scope, identifies missing test coverage for logic/integration work, and marks expected vs manual vs missing evidence.
  • Manual gate batches with platform options: Runs structured Batch 1 and Batch 2 stability/regression checks via questions, optionally performs Batch 3 data/performance checks (skipped in quick mode), and supports PC/Console/Mobile-specific smoke verification.
  • Actionable QA hand-off artifact: Produces a report and writes it to production/qa/smoke-[date].md after approval, enforcing the rule that a smoke-check fail blocks QA hand-off.

Quick Start

Run smoke-check for the sprint with platform coverage for all target devices by saying: start /smoke-check sprint --platform all.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I run a smoke test to gate builds before QA?

A build smoke test detects missing test setup, runs engine-specific automated suites, and performs manual stability checks to block broken releases from reaching QA.

How does smoke testing detect missing test coverage for sprint releases?

Smoke testing checks story scope to identify missing test coverage for logic and integration work, marking evidence as expected, manual, or missing before generating the QA gate report.

Can I run platform-specific smoke checks for PC, Console, and Mobile builds?

Yes, you can run platform-specific smoke checks by initiating sprint mode with platform coverage for all target devices, executing stability and regression batches tailored to each platform.

What is the difference between sprint mode and quick mode for build readiness checks?

Sprint mode runs all manual gate batches including data and performance checks, while quick mode skips Batch 3 performance checks to provide a faster build readiness verification.

How do automated tests select the right engine runner during a smoke check?

Automated tests select the engine runner by reading the Engine setting configured in the technical preferences document, ensuring the correct test execution framework is applied.

Where are smoke test reports saved for QA hand-off audits?

Smoke test reports are saved as auditable PASS/FAIL markdown files at production/qa/smoke-[date].md after approval, providing evidence for QA hand-off verification.