smoke-check

Execute smoke test suites and generate PASS/FAIL reports for release readiness.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill smoke-check-negentropy-laby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-check
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/smoke-check
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill smoke-check-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the gate between implementation and QA by running the critical path tests, evaluating core stability, and producing a PASS/FAIL report to prevent unvalidated builds from moving forward.

Core Features & Use Cases

  • Orchestrates environment detection and selects game or product domains for smoke testing.
  • Executes approved test suites, collects results, and generates a structured QA artifact for hand-off.
  • Supports per-sprint batches and platform-specific checks with optional quick mode for rapid re-checks.

Quick Start

Run a smoke-check against the current sprint to verify baseline stability before 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 tests to gate builds before QA hand-off?

Automated smoke tests gate builds by executing critical path test suites against the current sprint batch, evaluating core stability, and generating a structured PASS or FAIL report to prevent unvalidated releases from moving forward.

What is a smoke check process for release readiness in game and product projects?

A smoke check for release readiness automates environment detection, selects the game or product domain, executes approved test suites, and produces a QA artifact verifying baseline stability before hand-off.

Do I need a test framework and environment configuration to run automated smoke tests?

Yes, running automated smoke tests requires a test framework, a defined QA plan, and environment configuration to determine test scope and evaluate outcomes for release readiness.

Can I run platform-specific checks and quick re-checks during smoke testing?

Yes, smoke testing supports platform-specific checks alongside per-sprint batches, and includes an optional quick mode for rapid re-checks to verify baseline stability.

What is the best way to generate a QA artifact for release readiness?

The best way to generate a QA artifact for release readiness is to automate the gate between development and QA by executing critical path tests and collecting structured results for hand-off guidance.

Why use automated smoke tests instead of manual checks for CI gates?

Automated smoke tests prevent unvalidated builds from moving forward by orchestrating environment detection and executing approved test suites, ensuring consistent release readiness validation across per-sprint batches.