smoke-check

Executes smoke tests across React Native, Flutter, iOS and Android builds to generate PASS/FAIL verdicts.

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill smoke-check-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill smoke-check-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A blocking gate that runs before manual QA invests time. If smoke fails, manual QA stops and the build goes back to engineering.

Core Features & Use Cases

  • Phase-driven validation: verify build/target, read the smoke spec, run unit/integration tests, execute E2E smoke flows, and generate a verdict.
  • Cross-framework support: applicable to React Native, Flutter, iOS native, and Android native workflows.
  • Actionable outcomes: produces a PASS/FAIL report with flow-level details and health metrics for remediation.

Quick Start

Run the smoke-check against your latest build to generate a PASS/FAIL verdict.

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 tests to gate mobile builds before manual QA?

Automated smoke tests gate mobile builds by executing unit, integration, and E2E flows to produce a PASS/FAIL verdict. If the smoke check fails, the build returns to engineering and manual QA stops, preventing wasted effort on unstable releases.

Does automated smoke testing support React Native and Flutter workflows?

Automated smoke testing supports React Native, Flutter, iOS native, and Android native workflows. It delivers a flow-aware scope by validating the current build target and reading the corresponding smoke spec to run the matching automation.

What is the process for running pre-release smoke checks?

Pre-release smoke checks run phase-driven validation: verifying the build target, reading the smoke spec, executing unit and integration tests, running E2E smoke flows, and generating a final PASS/FAIL verdict with health metrics.

How do smoke test failures provide actionable details for remediation?

Smoke test failures provide actionable remediation details by capturing per-flow results and health probes alongside the final verdict. This flow-level reporting isolates exactly which unit, integration, or E2E validation failed.

Can I use E2E smoke tests as a blocking gate for iOS and Android native builds?

You can use E2E smoke tests as a blocking gate for iOS and Android native builds. The validation enforces guardrails by capturing per-flow results and health probes, halting the release process if the final verdict is FAIL.

Why should I run unit and integration tests before E2E smoke flows?

Running unit and integration tests before E2E smoke flows validates foundational build stability before executing complex end-to-end scenarios. This phase-driven approach ensures the target build is functional prior to full smoke test execution.