smoke-check

Run automated smoke tests and produce a PASS/FAIL gate report.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nevesb/idol-agency-maker --skill smoke-check-nevesb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/nevesb/idol-agency-maker/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/nevesb/idol-agency-maker --skill smoke-check-nevesb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a pre-QA gate by running automated and manual smoke checks, preventing incomplete or unstable builds from being handed to QA and wasting tester time.

Core Features & Use Cases

  • Automated test execution and parsing: selects and runs the appropriate test runner for the project's engine, collects test counts, failures and runner errors for a clear PASS/FAIL automated test row.
  • Coverage and story validation: compares sprint or QA plan stories against unit and integration test files to flag missing test evidence and produce coverage statuses per story.
  • Manual smoke verification and platform checks: batches interactive developer confirmations for core stability, sprint mechanics, data integrity, and optional platform-specific checks (PC, console, mobile), then assembles a dated QA smoke report and gates hand-off.
  • Use Case: After finishing a sprint, run this Skill to verify automated tests, validate coverage for sprint stories, perform quick manual checks, and produce a formal smoke-check report before QA receives the build.

Quick Start

Run the smoke-check skill with a command like /smoke-check sprint --platform all to execute tests, collect coverage and manual verifications, and prepare the smoke check report for approval.

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

To run a smoke test before QA, execute automated test runners, validate coverage against sprint stories, prompt for manual checks across platforms, and generate a PASS/FAIL gate report.

What is a build verification gate for sprint hand-offs?

A build verification gate for sprint hand-offs executes automated tests, checks story coverage, collects manual platform verifications, and produces a dated report to prevent broken builds from reaching QA.

Does automated smoke testing support console and mobile platforms?

Yes, automated smoke testing supports console and mobile platforms by batching interactive developer confirmations for optional platform-specific checks across PC, console, and mobile targets.

How do I verify test coverage against sprint stories?

Verify test coverage by comparing sprint or QA plan stories against unit and integration test files to flag missing test evidence and produce coverage statuses per story.

What is the best way to document manual smoke checks for QA?

The best way to document manual smoke checks is to batch interactive developer confirmations for core stability and data integrity, then optionally write a dated QA smoke report after approval.

Why do I need a QA gate for automated tests?

You need a QA gate for automated tests to prevent incomplete or unstable builds from being handed to QA, enforcing pre-QA checkpoints to save tester time by running smoke checks.