skills.rest
emcconnell
emcconnellCOMMUNITY
Explore all skills by this author →
GitHub

smoke-check

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

Updated Apr 10, 2026
Search Tags:#automation#testing#qa#ci#smoke-test#build-verification
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill smoke-check-emcconnell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/emcconnell/nova-scout --skill smoke-check-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the gate between implementation and QA by running the automated test suite, validating core functionality, and producing a PASS/FAIL report to prevent broken builds from progressing to QA.

Core Features & Use Cases

  • Automated test execution to detect regressions against the current build.
  • Generates a standardized PASS/FAIL smoke report and writes it to production/qa/smoke-[date].md for traceability.
  • Supports sprint and quick modes and optional platform scoping (--platform pc|console|mobile|all) to tailor checks to the current sprint's stories.
  • Use Case: After completing a sprint's stories, run smoke-check to gate the release before QA hand-off.

Quick Start

Run the smoke-check skill after a sprint's stories are implemented to gate the build before QA hand-off.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I automate build verification before QA hand-off?▼

Automated smoke testing gates builds before QA hand-off by running the test suite against current changes to validate core functionality and output a standardized PASS or FAIL verdict.

What is a smoke test report and where is it saved during CI?▼

A smoke test report documents automated build verification results and is written to production/qa/smoke-[date].md, providing traceability for QA sign-off and preventing broken builds from progressing.

How do I run quick smoke tests for a specific sprint platform?▼

Run smoke tests in quick or sprint modes using optional platform scoping (--platform pc|console|mobile|all) to tailor automated build verification checks to the current sprint's implemented stories.

Can I scope automated smoke tests to only check mobile or console builds?▼

Yes, automated smoke tests support platform scoping with --platform pc|console|mobile|all to tailor build verification checks specifically to the platform targeted by the current sprint's stories.

When should I run an automated smoke test suite during development?▼

Run an automated smoke test suite after completing a sprint's stories to gate the release and verify core functionality before manual QA hand-off, preventing broken builds from progressing further.

What limitations should I consider when gating builds with automated smoke tests?▼

Automated smoke tests validate core functionality and produce a PASS/FAIL verdict for QA gating but do not replace comprehensive manual QA, serving specifically to prevent broken builds from progressing.

Related Skills

Explore More Software Engineering Skills→
mvillmowmvillmow
18

run-tests

Execute Mojo or Pytest test suites and generate structured pass/fail reports.

Community
Intermediate
packetalienpacketalien

smoke-check

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

Community
Advanced
emcconnellemcconnell

team-qa

Coordinate QA team execution to produce test plans, cases, bug reports, and sign-off reports.

Community
Advanced
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced