!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