New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Smoke Check

by Donchitos in Donchitos/Claude-Code-Game-Studios

Critical-path smoke gate before QA hand-off — runs the automated suite.

MITAuto-check: notesTesting & QA

Install Smoke Check

skills CLI
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill smoke-check -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Donchitos/Claude-Code-Game-Studios smoke-check --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/smoke-check .claude/skills/smoke-check && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
smoke-check
GitHub stars
26k
Token cost
~1.2k tokens
SKILL.md length
618 words
Files
7 (incl. references)
Skills in repo
73
Repo updated
First seen
Licence
MIT

At a glance

Critical-path smoke gate before QA hand-off — runs the automated suite.

  • Works in 6 steps: Detect Test Setup → Run Automated Tests → Check Test Coverage → …
  • Testing & QA work in your project
  • SKILL.md covers Parse Arguments, Phase 1: Detect Test Setup, Phase 2: Run Automated Tests and Phase 3: Check Test Coverage, plus 4 more sections
  • Calls bash

What it does

Smoke Check is an agent skill from Donchitos/Claude-Code-Game-Studios. Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/1-detect-setup.md`, `references/2-run-tests.md` and `references/3-coverage.md`).

It sits in Testing & QA. The repository describes itself as: Turn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy. The licence is MIT.

When your agent uses it

  • Testing & QA work in your project

Example prompts

  • “/smoke-check”

Requirements

  • Pre-approved tools (allowed-tools): Read, Glob, Grep, Bash, Write, AskUserQuestion, Bash(bash "*/.claude/skills/smoke-check/../../hooks/yaml-helper.sh" resolve_config *)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Detect Test Setup
  2. Run Automated Tests
  3. Check Test Coverage
  4. Run Manual Smoke Checks
  5. Generate Report
  6. Write and Gate

What it can do on your machine

Read from SKILL.md and the folder at commit be8993b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Glob
    • Grep
    • Bash
    • Write
    • AskUserQuestion
    • Bash(bash "*/.claude/skills/smoke-check/../../hooks/yaml-helper.sh" resolve_config *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bash

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Smoke Check loads about 1.2k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 33 tokens; SKILL.md has 618 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~10k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Glob, Grep, Bash, Write, AskUserQuestion, Bash(bash "*/.claude/skills/smoke-check/../../hooks/

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Donchitos/Claude-Code-Game-Studios at commit be8993b, republished under its MIT licence (© Donchitos). 618 words, ~1,213 tokens.

Download SKILL.mdSave it as .claude/skills/smoke-check/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
smoke-check
description
Critical-path smoke gate before QA hand-off — runs the automated suite. A failed check means the build is not QA-ready.
allowed-tools
Read, Glob, Grep, Bash, Write, AskUserQuestion, Bash(bash "*/.claude/skills/smoke-check/../../hooks/yaml-helper.sh" resolve_config *)
argument-hint
[sprint | quick | --platform pc|console|mobile|all]
user-invocable
true
model
sonnet

!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level,testing.strict

Smoke Check

This skill is the gate between "implementation done" and "ready for QA hand-off". It runs the automated test suite, checks for test coverage gaps, batch-verifies critical paths with the developer, and produces a PASS/FAIL report.

The rule is simple: a build that fails smoke check does not go to QA. Handing a broken build to QA wastes their time and demoralises the team.

Output: production/qa/smoke-[date].md

Every AskUserQuestion call follows .claude/docs/automation-modes.md (collaborative asks always · guided major-only · autonomous logs and proceeds; automation_always_ask categories always prompt).

qa.level: at minimal, smoke-check is optional — if run, a FAIL is advisory and never blocks hand-off, and a project with no game tests is checked by its build, launch and critical paths alone (Phase 1 step 1); at standard, it is required before a phase transition; at full, before every commit. This sits in front of the Phase 6 testing.strict.config resolution (which only matters once a smoke run gates). Distinct axis from workflow.

Parse Arguments

Arguments can be combined: /smoke-check sprint --platform console

Base mode (first argument, default: sprint):

  • sprint — full smoke check against the current sprint's stories
  • quick — skip coverage scan (Phase 3) and Batch 3; use for rapid re-checks

Platform flag (--platform, default: none):

  • --platform pc — add PC-specific checks (keyboard, mouse, windowed mode)
  • --platform console — add console-specific checks (gamepad, TV safe zones, platform certification requirements)
  • --platform mobile — add mobile-specific checks (touch, portrait/landscape, battery/thermal behaviour)
  • --platform all — add all platform variants; output per-platform verdict table

If --platform is provided, Phase 4 adds platform-specific batches and Phase 5 outputs a per-platform verdict table in addition to the overall verdict.

Phase 1: Detect Test Setup

Read references/1-detect-setup.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 2: Run Automated Tests

Read references/2-run-tests.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 3: Check Test Coverage

Read references/3-coverage.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Show full SKILL.md (250 more words)Show less

Phase 4: Run Manual Smoke Checks

Read references/4-manual-checks.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 5: Generate Report

Read references/5-report.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Phase 6: Write and Gate

Read references/6-write-gate.md now and follow it — this phase's steps are in that file, not here. Read it again if the conversation was compacted or resumed during this phase.

Collaborative Protocol

Applies in collaborative mode (the default). For guided and autonomous modes, see .claude/docs/automation-modes.md — the rules below describe what collaborative mode requires, not universal behavior.

  • Never treat NOT RUN as automatic FAIL — record it as NOT RUN and let the developer confirm status manually. Unconfirmed NOT RUN yields NOT ASSESSED, not FAIL — and not a pass verdict either, which is what it used to yield.
  • Never auto-fix failures — report them and state what must be resolved. Do not attempt to edit source code or test files.
  • PASS WITH WARNINGS does not block QA hand-off — it records advisory gaps for /story-done to follow up on.
  • quick argument skips Phase 3 (coverage scan) and Phase 4 Batch 3. Use it for rapid re-checks after fixing a specific failure.
  • Use AskUserQuestion for all manual smoke check verification.
  • Never write the report without asking — Phase 6 requires explicit approval before any file is created.

© Donchitos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files (references) in .claude/skills/smoke-check of Donchitos/Claude-Code-Game-Studios.

  • SKILL.md
  • 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

Open the folder on GitHubat commit be8993b

Compare with similar skills

Smoke Check next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Smoke Check compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Smoke Check this skillDonchitos/Claude-Code-Game-Studios26k—~1.2kAutomated safety check: NotesMIT
Gm EvaluateRandallLiuXin/GodotMaker550—~4.7kAutomated safety check: PassCustom licence
Test Playable Web Gamesnirholas/three.ws2281 repos~429Automated safety check: PassApache-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Diagnosing Bugsfossasia/eventyay-interpretation1.6k32 repos~2.1kAutomated safety check: PassApache-2.0
TDDpietheinstrengholt/rssmonster56430 repos~906Automated safety check: PassMIT

Similar skills

  • Gm Evaluate

    RandallLiuXin/GodotMaker

    Evaluate the current tag's quality: enforce the playable-closed-loop gate, maintain a single cross-tag e2e/ suite that always reflects the current game (add tests for new mechanics, prune tests for…

    550 GitHub stars~4.7k tokensUpdated 22 days ago
    Testing & QAAuto-check passed

  • Test Playable Web Games

    nirholas/three.ws

    Test a playable browser game end to end with deterministic fixtures and real browser evidence.

    228 GitHub starsUsed in 1 repo~429 tokens
    Testing & QAAuto-check passed

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed

  • Diagnosing Bugs

    fossasia/eventyay-interpretation

    Diagnosis loop for hard bugs and performance regressions. An agent skill from fossasia/eventyay-interpretation.

    1.6k GitHub starsUsed in 32 repos~2.1k tokens
    Testing & QAAuto-check passed

  • TDD

    pietheinstrengholt/rssmonster

    Test-driven development. An agent skill from pietheinstrengholt/rssmonster.

    564 GitHub starsUsed in 30 repos~906 tokens
    Testing & QAAuto-check passed

  • TDD Workflow

    hellangleZ/burn-in-cceverywhere-ralph

    A skill your agent uses when writing new features, fixing bugs, or refactoring code.

    112 GitHub starsUsed in 11 repos~2.4k tokens
    Testing & QAAuto-check passed

More from Donchitos/Claude-Code-Game-Studios

All 73 skills in this repo

  • Architecture Decision

    Donchitos/Claude-Code-Game-Studios

    Create an ADR documenting a technical decision: context, alternatives considered, consequences.

    26k GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed

  • Dev Story

    Donchitos/Claude-Code-Game-Studios

    Implement a story: ADR guidelines, right programmer agent, code plus test.

    26k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check: notes

  • Game Asset Audit

    Donchitos/Claude-Code-Game-Studios

    Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.

    26k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Game Asset Spec Writer

    Donchitos/Claude-Code-Game-Studios

    Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.

    26k GitHub stars~5k tokensUpdated yesterday
    Auto-check passed

  • Game Balance Check

    Donchitos/Claude-Code-Game-Studios

    Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.

    26k GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Structured Bug Reports

    Donchitos/Claude-Code-Game-Studios

    Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.

    26k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check: notes

Categories

Questions about Smoke Check

What does Smoke Check do?

Critical-path smoke gate before QA hand-off — runs the automated suite. Smoke Check is an agent skill from Donchitos/Claude-Code-Game-Studios. Critical-path smoke gate before QA hand-off — runs the automated suite.

When should I use Smoke Check?

Smoke Check fits situations like: testing & QA work in your project.

How do I install Smoke Check in Claude Code?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill smoke-check -a claude-code`. Or copy the skill folder (.claude/skills/smoke-check in Donchitos/Claude-Code-Game-Studios) into .claude/skills/smoke-check in your project. Claude Code loads it when a task matches its description.

How do I install Smoke Check in Codex?

Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill smoke-check -a codex`. Or copy the skill folder (.claude/skills/smoke-check in Donchitos/Claude-Code-Game-Studios) into .agents/skills/smoke-check in your project. Codex loads it when a task matches its description.

Can I use Smoke Check in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Donchitos/Claude-Code-Game-Studios --skill smoke-check -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/smoke-check, .gemini/skills/smoke-check, .github/skills/smoke-check and .opencode/skills/smoke-check in your project.

What does Smoke Check need to run?

Going by SKILL.md and its folder, Smoke Check needs the command-line tools its instructions call (bash). Its frontmatter pre-approves these tools: Read, Glob, Grep, Bash, Write, AskUserQuestion, Bash(bash "*/.claude/skills/smoke-check/../../hooks/yaml-helper.sh" resolve_config *).

Does Smoke Check access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Smoke Check safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Smoke Check use?

Smoke Check is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Smoke Check use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 9k tokens, read only when the agent opens those files.

What are the alternatives to Smoke Check?

Skills that share tags, products or a category with Smoke Check: Gm Evaluate (RandallLiuXin/GodotMaker, 550 stars), Test Playable Web Games (nirholas/three.ws, 228 stars), Web Application Testing (anthropics/skills, 180k stars) and Diagnosing Bugs (fossasia/eventyay-interpretation, 1.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Smoke Check?

Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 25,951 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on October 8, 2026.

Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.