smoke-check

Run automated smoke checks and generate a PASS/FAIL QA hand-off report.

18|5|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill smoke-check-wsman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/smoke-check
Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill smoke-check-wsman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken builds from reaching QA by combining automated test execution, core workflow verification, and a clear PASS/FAIL gate before hand-off.

Core Features & Use Cases

  • Automated test run: Detects the project stack, runs the appropriate test command, and captures failures or unavailable runners.
  • Coverage review: Scans sprint or QA-plan stories for matching test evidence and flags logic or integration gaps that still need coverage.
  • Manual smoke verification: Guides the operator through core stability, integration, data integrity, and platform-specific checks for product or game projects.
  • QA reporting: Produces a structured report with verdicts, missing evidence, and follow-up guidance for QA and development teams.

Quick Start

Ask for a smoke check on the current sprint so the Skill can run tests, verify coverage, collect manual results, and prepare a QA hand-off 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 a smoke test before QA hand-off to verify build readiness?

To run a smoke test before QA hand-off, the Skill detects your project stack, executes the appropriate test command, and guides manual core-path verification to produce a structured PASS/FAIL gate report.

What is a release gate for QA hand-off and how does it work?

A release gate for QA hand-off is a verification barrier that runs automated smoke tests and manual checks to ensure a build is stable. It produces a PASS/FAIL verdict with evidence before release candidates move to QA.

How do I check test coverage gaps for sprint stories before release?

To check test coverage gaps, the Skill scans sprint or QA-plan stories for matching test evidence and flags missing logic or integration coverage, reporting what still needs verification before the build proceeds to QA.

Does the smoke check process work for both game and product repositories?

Yes, the smoke check process supports both game and product repositories, applying platform-specific smoke batches, environment detection, and manual verification for core stability, integration, and data integrity.

What happens when automated test runners are unavailable during a smoke check?

When automated test runners are unavailable, the Skill captures the runner failure or unavailability status within its execution report, ensuring the missing evidence is documented in the final PASS/FAIL QA hand-off verdict.

Will the smoke check automatically fix failing tests in my build?

No, the smoke check does not auto-fix failures. It strictly executes tests, verifies coverage, guides manual core-path checks, and logs gated evidence to report failures for the development team to resolve.