smoke-check

Run automated smoke tests and generate a PASS/FAIL readiness report.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill smoke-check-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/WindXRan/y3td --skill smoke-check-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken or unverified builds from reaching QA by running automated tests, checking coverage gaps, and collecting manual smoke confirmations into a single pass/fail gate.

Core Features & Use Cases

  • Automated critical-path verification: Runs the project test suite when possible and summarizes pass/fail counts plus up to 10 failing test names.
  • Coverage and evidence gap detection: Compares sprint/QA-plan stories against expected unit/integration tests and flags missing evidence without blocking solely for advisory gaps.
  • Interactive manual smoke batching: Uses guided multi-select checks (and optional platform-specific batches) to validate runtime health beyond automated coverage.
  • Verdict-grade reporting and gating: Produces a structured production/qa/smoke-[date].md report with clear PASS / PASS WITH WARNINGS / FAIL rules to decide QA hand-off readiness.

Quick Start

Run smoke-check with sprint mode to validate readiness before QA, for example: /smoke-check sprint --platform pc.

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 before QA hand-off to prevent broken builds?

To run a smoke test before QA hand-off, execute a sprint mode command with optional platform flags. The skill runs automated tests, scans coverage evidence for sprint stories, and collects manual checks into a structured PASS/FAIL gate report at production/qa/smoke-[date].md.

What is a QA gate and how does it handle unverified test coverage?

A QA gate is a pass/fail checkpoint preventing unverified builds from reaching QA. It flags missing coverage evidence for sprint stories as advisory warnings rather than hard failures, ensuring gaps are visible without blocking the pipeline.

Can I perform platform-specific smoke testing for PC, console, and mobile builds?

Yes, you can perform platform-specific smoke testing for PC, console, and mobile builds. The skill applies optional platform-specific interactive manual check batches to validate runtime health beyond standard automated coverage.

How does automated smoke testing handle engine detection and test runner outcomes?

Automated smoke testing selects the correct test command based on engine detection, extracts runner outcomes, and summarizes pass/fail counts plus up to 10 failing test names to verify critical-path readiness.

What are the verdict rules for a PASS WITH WARNINGS result in smoke checking?

In smoke checking, NOT RUN statuses are treated as warnings until manually confirmed, resulting in a PASS WITH WARNINGS verdict. A FAIL verdict is enforced when critical automated tests fail or manual checks uncover blocking issues.

What is the best way to document manual smoke check results for sprint readiness?

The best way to document manual smoke check results is using guided multi-select checks to batch runtime health validations. This generates a dated markdown report at production/qa/smoke-[date].md with clear pass/fail gate rules.