Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
Passed 17 of 18 test cases with the skill, and 6 of 18 without it.
and 11 more in the full report
11 fixed6 passed either way1 still failing0 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
When performing Phase 1 setup detection during a smoke check run, where are the detailed execution steps defined?
| Checked | Without skill | With skill |
|---|---|---|
| References references/1-detect-setup.md. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,qa.level,testing.strict
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.
Arguments can be combined: /smoke-check sprint --platform console
Base mode (first argument, default: sprint):
sprint — full smoke check against the current sprint's storiesquick — skip coverage scan (Phase 3) and Batch 3; use for rapid re-checksPlatform 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,test cases passed, vs 6 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.