skills.rest
solace-ill
solace-illCOMMUNITY
Explore all skills by this author →
GitHub

smoke-check

Run automated test suites and produce PASS/FAIL reports for QA hand-off.

Updated Apr 26, 2026
Search Tags:#automation#testing#qa#platform#sprint#smoke-check
One-click install
npx skills add https://github.com/solace-ill/vector-flow --skill smoke-check-solace-ill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/solace-ill/vector-flow/tree/main/.claude/skills/smoke-check
Command: npx skills add https://github.com/solace-ill/vector-flow --skill smoke-check-solace-ill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate QA between implementation and QA hand-off by running the automated test suite, validating core functionality, and producing a PASS/FAIL report.

Core Features & Use Cases

  • Runs the automated test suite and collects results to determine readiness for QA.
  • Verifies core functionality across critical paths and reports PASS/FAIL status.
  • Supports platform-aware and sprint-based configurations to tailor checks before hand-off.

Quick Start

Run /smoke-check sprint after a sprint's stories are implemented to gate QA hand-off.

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 testing before QA hand-off?▼

Automated smoke testing verifies core functionality across critical paths by running the test suite and collecting results. It determines readiness for QA hand-off by producing a PASS/FAIL report based on sprint stories and platform variants.

When do I need a smoke test gate in my sprint workflow?▼

A smoke test gate is needed after sprint stories are implemented and before QA hand-off. It executes automated checks to validate critical paths, ensuring platform variants and CI artifacts pass before manual QA evaluation begins.

Can I run platform-specific smoke checks for different environments?▼

Yes, platform-aware smoke checks support different environments by tailoring configurations before QA hand-off. The automated test suite evaluates platform variants and produces per-run reporting with PASS/FAIL status for each specific check.

What is the best way to gate QA with automated test results?▼

The best way to gate QA with automated test results is running the test suite to validate critical paths and generating a PASS/FAIL report. This approach specifies required test frameworks and QA plan references for structured per-run reporting.

Does smoke-check work with sprint-based QA configurations?▼

Yes, smoke-check supports sprint-based QA configurations by evaluating implemented stories and platform variants. It runs automated test suites to validate core functionality and produces PASS/FAIL reports tailored for QA hand-off readiness.

Why use automated smoke checks instead of manual QA validation?▼

Automated smoke checks provide a consistent gate between implementation and QA by running test suites and producing PASS/FAIL reports. This reduces manual effort by validating critical paths and platform variants before hand-off.

Related Skills

Explore More Software Engineering Skills→
rakhnianskii9rakhnianskii9

smoke-check

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

Community
Advanced
emcconnellemcconnell

smoke-check

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

Community
Advanced
luokai25luokai25

test-automator

Develop test automation frameworks, scripts, and CI/CD pipeline integrations.

Community
Advanced
striderZAstriderZA
72

smoke-check

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

Community
Advanced