One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill smoke-check-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/smoke-check
Command: npx skills add https://github.com/MichaelSolati/mkai --skill smoke-check-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams frequently waste QA time and demoralize staff by handing off unstable, broken builds for testing. This skill eliminates that risk by enforcing a formal pre-QA gating process that validates build stability, test coverage, and critical path functionality before hand-off.

Core Features & Use Cases

  • Automated Test Execution: Runs test suites for Godot 4, Unity, and Unreal Engine projects, parsing results to count passes, failures, and crash errors.
  • Coverage Gap Detection: Scans sprint stories to identify logic and integration tests that are missing, flagging gaps that must be resolved before stories can be marked complete.
  • Manual Critical Path Verification: Batch-asks developers to confirm core stability, sprint changes, and platform-specific functionality work as expected.
  • Formal Report Generation: Produces a dated PASS/FAIL report with clear verdicts, missing test evidence, and platform-specific results to guide QA hand-off. Use Case: A game dev team finishing a 2-week sprint can run this skill to confirm their build is stable, catch missing test coverage for new combat mechanics, and get a clear go/no-go decision before sending the build to QA.

Quick Start

Use the smoke-check skill to run a full sprint smoke test for your current game build before handing it off to QA.

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 on my game build before handing it off to QA?

Run a pre-QA smoke test to validate game build stability by executing automated test suites, scanning sprint stories for missing coverage, and verifying critical paths to generate a formal PASS or FAIL gating report.

Does automated build validation work with Unity, Unreal Engine, and Godot projects?

Yes, automated build validation works with Godot, Unity, and Unreal Engine projects by parsing test suite results to count passes, failures, and crash errors before allowing a QA hand-off.

What is pre-QA gating for sprint builds and why is it needed?

Pre-QA gating for sprint builds is a formal validation process that prevents unstable game builds from reaching QA, eliminating wasted testing effort and team frustration by enforcing test coverage and critical path checks.

How do I track missing test evidence for new game mechanics before a QA hand-off?

Track missing test evidence by scanning sprint stories to identify missing logic and integration tests, flagging coverage gaps that must be resolved before stories can be marked complete for QA.

Can I batch verify manual critical paths and platform-specific functionality for a game release?

Yes, you can batch-ask developers to confirm core stability, sprint changes, and platform-specific functionality, ensuring manual critical path verification is documented before generating the final QA hand-off report.

What is the best way to generate a formal PASS/FAIL report for game build validation?

Generate a formal PASS/FAIL report by executing automated test suites and coverage scans, then compiling dated verdicts, missing test evidence, and platform-specific results to guide the final game build QA hand-off decision.