Skip to content
Get packs

Smoke Check Gate

Runs an automated critical-path check on a game build before handing it to QA

Source Download skill
Repository
Donchitos/Claude-Code-Game-Studios
Stars
32,965
Licence
MIT
Files
7 files

What it does

When you ask your AI agent to run a smoke check, it follows a six-phase procedure: it detects how the project's tests are set up, runs the automated test suite (for example Godot headless or Unity tests), looks for coverage gaps, walks you through manual critical-path checks by asking questions, and writes a PASS/FAIL report to production/qa/. A failed check is meant to mean the build is not ready for QA hand-off. The skill is written for game projects and its own instructions say it should not auto-fix failures.

Great for

  • Game developers who want a consistent checklist before sending a build to testers
  • Teams using the Claude Code Game Studios setup who run smoke checks at sprint or phase boundaries
  • Leads who want a written PASS/FAIL record of each build's critical-path status

Skip it if

  • Non-game software projects, since the detection and test commands target Godot and Unity setups (reason: the commands and checks will not match other stacks)
  • Teams wanting a fully automatic verdict, since manual checks are confirmed through questions and unconfirmed items are marked NOT ASSESSED (reason: the result depends on your answers)
  • Projects where running Godot or Unity test commands on the machine is not acceptable, since the skill executes them (reason: it runs local scripts and commands)

Try asking

  • “Run a smoke check on the current sprint before we hand the build to QA”
  • “Do a quick smoke check on the console build, I just fixed the login crash”
  • “Run a smoke check with --platform all and show me a per-platform verdict table”
Step-by-step guide: how to use Smoke Check GateInstall, first run, examples, tips and FAQs

Install in 3 steps

  1. 1

    Download the skill

    The ZIP contains the 7 original files, the MIT licence and an attribution note.

    smoke-check.zip
  2. 2

    Add it to your agent

    Claude Code (all projects)

    mkdir -p ~/.claude/skills && unzip smoke-check.zip -d ~/.claude/skills/

    Claude Code / Agent SDK (this project only)

    mkdir -p .claude/skills && unzip smoke-check.zip -d .claude/skills/

    Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.

  3. 3

    Ask for the task

    No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.

Get better results

  • Start with the quick argument for rapid re-checks after fixing one specific failure, since it skips coverage scanning and one manual batch
  • Answer the manual check questions honestly; anything you do not confirm is recorded as NOT ASSESSED rather than passed
  • Review the Bash commands the skill is allowed to run before approving it, since it executes Godot with a timeout of up to 30 minutes and writes report files

What's inside

  • references/1-detect-setup.md
  • references/2-run-tests.md
  • references/3-coverage.md
  • references/4-manual-checks.md
  • references/5-report.md
  • references/6-write-gate.md
  • SKILL.md

Redistributed unmodified from Donchitos/Claude-Code-Game-Studios under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.