smoke-check

Automate critical path smoke testing and generate QA readiness reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or unstable builds from reaching the QA team by automating the critical path verification process and enforcing a strict PASS/FAIL gate.

Core Features & Use Cases

  • Automated Test Execution: Runs engine-specific test suites (Godot, Unity, Unreal) to verify code integrity.
  • Coverage Analysis: Maps sprint stories to test files to identify gaps in logic or integration testing.
  • Manual Smoke Verification: Orchestrates batch-based user checks for core stability, platform-specific behaviors, and performance.
  • Use Case: Before handing off a new sprint build to QA, run this skill to ensure all core mechanics are stable and documented, preventing wasted QA cycles on broken features.

Quick Start

Run the smoke check skill to verify the current sprint build and generate a full QA readiness report.

Frequently Asked Questions about smoke-check

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

FAQPage Schema
How do I automate smoke testing for game builds before handing them off to QA?

Automated smoke testing for game builds executes engine-specific test suites and generates a formal PASS/FAIL report to verify core stability. This ensures only validated, stable builds reach the QA team, preventing wasted QA cycles on broken features.

Does automated smoke testing support Unity, Unreal, and Godot game engines?

Automated smoke testing supports Unity, Unreal, and Godot game engines. It runs engine-specific test suites to verify code integrity across different game development platforms before generating a QA readiness report.

How does coverage analysis map sprint stories to automated tests?

Coverage analysis maps sprint stories to test files to identify gaps in logic or integration testing. This verifies that all sprint requirements have corresponding tests before a build passes the QA readiness gate.

What is the best way to verify platform-specific stability for a new sprint build?

The best way to verify platform-specific stability is orchestrating batch-based manual smoke verification alongside automated test execution. This combination checks core stability and platform-specific behaviors, generating a formal PASS/FAIL report for QA handoff.

Can I integrate a PASS/FAIL gate into my CI/CD pipeline for game development?

You can integrate a PASS/FAIL gate into your CI/CD pipeline for game development by running automated smoke tests during the build process. This enforces a strict gate that blocks broken or unstable builds from reaching the QA team.

Why do unstable builds keep reaching my QA team and how can I prevent it?

Unstable builds reach QA when critical path verification is manual or skipped. Automating smoke tests and enforcing a strict PASS/FAIL gate prevents broken builds from advancing, ensuring QA only receives validated, stable sprint builds.