smoke-check

Run automated smoke tests and generate a PASS/FAIL report.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/rakhnianskii9/God-Godot --skill smoke-check-rakhnianskii9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/rakhnianskii9/God-Godot/tree/main/.github/skills/smoke-check
Command: npx skills add https://github.com/rakhnianskii9/God-Godot --skill smoke-check-rakhnianskii9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the gate between implementation and QA by executing a standardized smoke test suite and generating a PASS/FAIL report.

Core Features & Use Cases

  • Automates the smoke test gate to prevent QA hand-off when the build fails.
  • Supports sprint validation and platform-specific batches via optional arguments.
  • Integrates with existing CI workflows to surface a clear report path for remediation.

Quick Start

Run the smoke-check to gate the current sprint build before QA.

Frequently Asked Questions about smoke-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate smoke checks before a QA hand-off?

Automated smoke checks gate your build by running a standardized test suite and generating a PASS/FAIL report before QA hand-off. This prevents passing a failed build to the QA team and provides a clear remediation path.

Can I run platform-specific smoke tests for Godot game builds?

Yes, you can run platform-specific smoke tests for Godot builds using the --platform argument. Supported options include pc, console, mobile, or all, allowing you to tailor the test scope to your target platform variants.

How does a smoke test gate integrate with existing CI workflows?

Smoke test gates integrate with CI workflows by executing the automated suite during the pipeline and surfacing a clear report path. If the suite fails, the gate stops the pipeline to prevent a broken build from reaching QA.

What is the difference between sprint and quick smoke test scopes?

Sprint and quick scopes tailor the smoke test execution range. Sprint validation runs the full suite for sprint completion, while the quick option executes a faster, targeted batch to verify basic build stability rapidly.

Does the smoke check validate the test environment and engine detection?

Yes, the smoke check satisfies environment checks by validating test setup, CI configuration, and engine detection. This ensures the testing environment is correctly configured before executing the automated suite.

What happens when an automated smoke test suite fails?

When an automated smoke test suite fails, the gate stops the build and outputs guidance for remediation. This report directs developers to the specific failures to fix before attempting another QA hand-off.