skills.rest
JunnnnyWon
JunnnnyWonCOMMUNITY
Explore all skills by this author →
GitHub

smoke-check

Run the automated test suite and generate a PASS/FAIL smoke-test report.

Updated Aug 23, 2026
Search Tags:#automation#testing#qa#ci-cd#quality-assurance#smoke-test
One-click install
npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill smoke-check-junnnnywon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/JunnnnyWon/Codex-Game-Studios/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/JunnnnyWon/Codex-Game-Studios --skill smoke-check-junnnnywon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the gate between implementation completion and QA hand-off by running the automated test suite, ensuring only builds that pass the smoke test proceed to QA.

Core Features & Use Cases

  • Automates running the automated test suite to catch critical regressions before hand-off.
  • Produces a concise PASS/FAIL smoke report to guide QA decisions.
  • Integrates into sprint closures, pre-QA hand-off, and CI pipelines to protect the release.

Quick Start

Initiate a sprint smoke-check by running /smoke-check sprint.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I automate a smoke test before QA hand-off?▼

Automating a smoke test before QA hand-off requires running your automated test suite to verify core paths. This skill executes those tests at sprint closure or pre-QA to generate a structured PASS/FAIL report, ensuring only verified builds proceed to manual testing.

Can I run a smoke test gate within my CI pipelines?▼

Yes, you can run a smoke test gate within CI pipelines. This skill integrates into CI pipelines to execute automated tests, verify core application paths, and output a structured smoke-test report that protects the release process from critical regressions.

What is a smoke test report and when do I need it?▼

A smoke-test report is a concise PASS/FAIL document generated after running automated tests. You need it at sprint closure, before manual QA, or within CI pipelines to verify core paths and guide QA hand-off decisions.

Do I need a test framework in place to use automated smoke testing?▼

Yes, you need a test framework in place and engine configuration to drive test execution. This skill automates the test suite execution and gate logic, but relies on your existing testing framework to run the actual smoke tests.

How do I catch critical regressions at sprint closure?▼

To catch critical regressions at sprint closure, you can run an automated smoke test. This skill executes your test suite to verify core paths, producing a PASS/FAIL report that gates the build before QA hand-off.

Related Skills

Explore More Software Engineering Skills→
GenEducationGenEducation

bmad-qa-generate-e2e-tests

Generate framework-aware API and end-to-end test suites for existing codebase features.

Official
Advanced
wsmanwsman
18

smoke-check

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

Community
Advanced
J03Fr0stJ03Fr0st

ci-cd-and-automation

Automate CI/CD pipeline setup with GitHub Actions and quality gates.

Community
Advanced
newkayak12newkayak12
1

test-master

Generates test files, strategies, and defect reports for functional, performance, and security testing.

Community
Advanced