smoke-testlisted

Designs and scaffolds smoke-test suites (build-verification tests) for web services, APIs, and software systems. Use this skill whenever the user asks to "add smoke tests", "set up build verification", "write a fast test that proves the deploy isn't broken", "what should my smoke tests cover", "wire smoke tests into CI", or anything else about catching catastrophic failures before downstream testing. Also trigger on "BVT / BAT", "intake testing", "sanity vs smoke", "build acceptance". The skill detects the project's stack (Python/FastAPI, Node/Express, Go net/http, Rust/axum, etc.), proposes a focused 5-10 check suite following the API-first, <2-minute, idempotent discipline, and emits a runnable scaffold in the right framework — with `TODO` markers for environment-specific values like base URL and auth tokens. Even if the user has not explicitly said "smoke", trigger when they ask for a "fast CI gate", "deploy-readiness check", "is-the-build-up test", "happy-path coverage", or describe symptoms like "we keep
Stoica-Mihai/claude-skills · ★ 0 · AI & Automation · score 72

Install: claude install-skill Stoica-Mihai/claude-skills

# Smoke Test A smoke test (a.k.a. build-verification test / build-acceptance test / intake test) is a small, fast, broad-but-shallow suite that verifies a fresh build is *stable enough to bother testing further*. It is the release gate that protects the rest of the pipeline from wasting time on fundamentally broken code. The name comes from electrical engineering: power on the board and watch for smoke. If it smokes, stop. This skill helps you design + scaffold one for the user's project. It is **not** a regression-suite generator and not a full QA strategy: smoke tests stay focused on a handful of critical happy-paths and connectivity checks. ## When to invoke this skill Use it when the user wants any of: - A *new* smoke-test suite for a service that has none - A review of an *existing* smoke-test suite for scope, speed, flakiness - CI/CD wiring so smoke runs as a gate before regression - Help picking the 5-10 checks that should make the cut Skip it for: - Unit testing or full regression testing (different discipline, larger scope) - Pure performance / load testing (overlaps but lives elsewhere) - "Fix this failing test" — that is debugging, not suite design ## Core principles (compressed) Smoke tests have a different shape from other tests. The user may not know these, so anchor every recommendation in them: - **Broad, not deep.** Cover the most important user-facing paths. Skip edge cases, validation rules, error-message wording. If the smoke suite is faili