smoke

Execute automated smoke tests against a running Docker stack.

10|2|Updated Mar 2, 2026

Search Tags:#automation #qa #docker #ci-cd #api-testing #health-check #smoke-testing

Ready to run

npx skills add https://github.com/dixus/claudeframework --skill smoke-dixus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smoke
Source: https://github.com/dixus/claudeframework/tree/main/.claude/skills/smoke
Command: npx skills add https://github.com/dixus/claudeframework --skill smoke-dixus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running deployments often lacks quick end-to-end validation. This Skill provides a fast, repeatable way to confirm that a Docker stack behaves as expected by executing lightweight smoke tests against a live environment.

Core Features & Use Cases

Health-check verification: polling the health endpoint and container status to verify uptime.
Spec-driven smoke testing: automatically locate or create a smoke test file to validate critical API routes.
CI/CD compatibility: integrates into pipelines to catch regressions immediately after deployment.

Quick Start

Run the smoke tests against the running Docker stack for a spec.

Frequently Asked Questions about smoke

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

FAQPage Schema

How do I run automated smoke tests against a running Docker stack?▼

To run smoke tests against a Docker stack, execute the skill to automatically detect a test spec, derive the runner from its file extension, and validate critical API routes via health endpoints without modifying application code.

Can I integrate API health-check verification into my CI/CD pipeline?▼

Yes, you can integrate API health-check verification into CI/CD pipelines to catch regressions immediately after deployment by polling container status and health endpoints to verify uptime and end-to-end behavior.

What is the best way to validate API routes after deploying a Docker stack?▼

Spec-driven smoke testing is the best way to validate API routes after deployment, automatically locating or creating a smoke test file to execute lightweight end-to-end checks against the live Docker environment.

Do I need to modify my application code to verify end-to-end behavior?▼

No, you do not need to modify application code to verify end-to-end behavior; the skill validates API routes and checks container health by interacting with the running Docker stack externally.

How does spec-driven smoke testing determine which test runner to use?▼

Spec-driven smoke testing determines the appropriate test runner by deriving it directly from the file extension of the detected smoke test spec, which can be explicitly specified or automatically selected as the most recently modified.

Why use lightweight smoke tests instead of full QA automation for Docker deployments?▼

Lightweight smoke tests provide a fast, repeatable way to confirm critical API routes and uptime immediately after deployment, catching regressions quickly without the overhead of full QA automation suites.