
Smoke Check
Execute smoke test gate before QA hand-off with automated verification
What You Can Do
Smoke Check executes your automated test suite against the current sprint's implementation, verifies test coverage for critical paths, and produces a definitive PASS/FAIL gate report. You can run full sprint validation or quick re-checks, add platform-specific test batches (PC, console, mobile), and generate per-platform verdict tables. A failed smoke check immediately signals the build isn't ready for QA, preventing wasted QA cycles and team morale issues.
Features
runs complete automated test suite against all sprint stories
skip coverage scans for rapid validation after fixes
add PC, console, or mobile verification (keyboard, gamepad, touch, TV safe zones)
identifies untested critical paths before QA hand-off
outputs separate PASS/FAIL verdicts for each platform variant
prompts developer to confirm critical path assumptions before testing
generates timestamped report in production/qa/ directory
automatically identifies and validates your test setup
Example Output
Overall Verdict: PASS
Test Results Summary
- Total Tests: 247
- Passed: 245
- Failed: 2 (non-critical)
- Coverage Gap Warnings: 0
Critical Path Status
- User login → dashboard: ✓ PASS
- Payment processing: ✓ PASS
- Data export: ✓ PASS
Platform Verdicts (when using --platform all)
- PC: PASS (keyboard, mouse, windowed mode verified)
- Console: PASS (gamepad input, TV safe zones verified)
- Mobile: PASS (touch, portrait/landscape rotation verified)
Report saved to: production/qa/smoke-2024-01-15.md
What's Included
- `SKILL.md` instruction file with Phase 1-5 workflow:
- Smoke test configuration template for test framework detection:
- Platform-specific test batch templates (PC, console, mobile):
- Critical path verification checklist:
- PASS/FAIL report markdown template with verdict table structure:
Who It's For
- QA Engineers — enforce build quality gates before accepting builds
- Release Engineers — automate pre-release smoke testing workflows
- Scrum Masters — validate sprint completion before QA ceremonies
- Development Leads — ensure team code quality standards before hand-off
- DevOps/Build Engineers — integrate smoke checks into CI/CD pipelines
Best For
- Pre-QA build validation — gate check before manual testing begins
- Multi-platform release verification — validate PC, console, and mobile builds
- Sprint completion checks — verify all sprint stories meet smoke test criteria
- Rapid re-validation after fixes — quick mode for testing hotfixes and patches
- Coverage gap identification — detect untested critical paths before QA cycles







