skills.rest
imgamer
imgamerCOMMUNITY
Explore all skills by this author →
GitHub

smoke-check

Execute engine-aware smoke tests and write a QA report to production/qa/smoke-[date].md.

Updated Dec 22, 2024
Search Tags:#test automation#game engine#smoke testing#coverage verification#platform certification#qa handoff#pass fail reporting
One-click install
npx skills add https://github.com/imgamer/AILearn --skill smoke-check-imgamer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/imgamer/AILearn/tree/main/game-studios/Claude-Code-Game-Studios-e375f/.claude/skills/smoke-check
Command: npx skills add https://github.com/imgamer/AILearn --skill smoke-check-imgamer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken game builds from reaching manual QA by running an automated smoke-test gate and producing an actionable PASS/FAIL outcome.

Core Features & Use Cases

  • Automated test execution: Runs the project’s test suite (engine-aware) and summarizes pass/fail counts and failing test names.
  • Coverage gap detection: Compares sprint story scope against expected test evidence and flags missing or manual-only coverage as advisories.
  • Guided manual smoke checks: Uses batched questions (AskUserQuestion) to verify core gameplay behavior and regressions, plus optional per-platform checks.

Quick Start

Run smoke-check in sprint mode to test the current sprint’s critical paths and generate a QA-ready PASS/FAIL report for 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 run smoke tests on a game build before handing it off to QA?▼

Run sprint-based smoke tests to gate game builds before QA handoff by executing the engine-aware test runner, evaluating sprint story coverage, and guiding manual stability checks to produce a clear PASS or FAIL outcome.

What is automated smoke testing for sprint-based release gating?▼

Automated smoke testing for sprint-based release gating executes your project's test suite, compares sprint story scope against expected test evidence, and flags missing coverage as advisories to prevent broken game builds from reaching manual QA.

Can I verify platform certification and core gameplay regressions during smoke testing?▼

Yes, you can verify core gameplay behavior and regressions during smoke testing by using batched user confirmations, which also support optional per-platform checks to ensure comprehensive stability before QA handoff.

How do I generate a QA report for smoke test pass fail results?▼

Generate a QA-ready smoke test report by summarizing automated pass fail counts and failing test names, then writing the production QA handoff document directly to production/qa/smoke-[date].md.

Does the smoke testing process require engine detection to run the test runner?▼

Yes, smoke testing requires engine detection from technical preferences to identify and run the appropriate engine-aware test runner for executing the project's test suite and gathering coverage evidence.

What is the best way to detect coverage gaps in game engine smoke tests?▼

The best way to detect coverage gaps is to compare sprint story scope against expected test evidence, automatically flagging any missing or manual-only coverage as advisories in the final QA smoke report.

Related Skills

Explore More Software Engineering Skills→
easonlaoeasonlao

test-setup

Create engine-specific test directories and GitHub Actions workflow files.

Community
Intermediate
brand6brand6

smoke-check

Run automated smoke tests and generate PASS/FAIL reports for QA readiness.

Community
Advanced
jmaglyjmagly
175

gate-evaluation

Validate phase-gate criteria and generate pass/fail gate reports.

Community
Advanced
junchenghuojunchenghuo
3

qa-regression-checklist

Generate regression and smoke test checklists for software releases.

Community
Basic