smoke-test-runner

Run post-deploy sanity checks with five canonical critical path validations.

3|2|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/robotijn/ctoc --skill smoke-test-runner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smoke-test-runner
Source: https://github.com/robotijn/ctoc/tree/main/skills/testing/runners/smoke-test-runner
Command: npx skills add https://github.com/robotijn/ctoc --skill smoke-test-runner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of broken deployments reaching users by running fast, narrow sanity checks immediately after every deploy to catch obvious failures before traffic is ramped up.

Core Features & Use Cases

  • 5 Canonical Critical Checks: Validates health endpoint response, database connectivity, auth path functionality, primary user-facing path, and deployed build version match.
  • Automated Rollback Integration: Non-zero exit codes trigger platform-specific rollback commands (Kubernetes, Vercel, Cloud Run, ArgoCD) to revert failed deploys automatically.
  • Cross-Platform Support: Includes pre-configured patterns for Playwright, k6, pytest, .NET, Spring Boot, and shell-based curl/sql probes for any tech stack.
  • Dual Use Case: Works as both a post-deploy pipeline gate and a continuous synthetic monitor that re-runs the same checks every 1-5 minutes in production.
  • Use Case Example: After deploying a new version of your e-commerce API, run this skill to confirm the health endpoint, sign-in flow, and product listing endpoint are working before routing customer traffic to the new build.

Quick Start

Use the smoke-test-runner skill to execute post-deploy sanity checks for your latest application deployment and confirm all critical paths are functional before ramping user traffic.

Frequently Asked Questions about smoke-test-runner

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

FAQPage Schema
How do I run post-deploy smoke tests to catch broken deployments before routing traffic?

Post-deploy smoke tests execute five canonical critical path checks—health endpoints, database connectivity, auth paths, primary user paths, and build versions—to catch deployment failures before user traffic ramps up. The suite completes in under two minutes using parallel-safe probes.

Can I trigger automated rollback on Kubernetes or Vercel when a post-deploy sanity check fails?

Automated rollback triggers via non-zero exit codes execute platform-specific rollback commands for Kubernetes, Vercel, Cloud Run, and ArgoCD. Failed post-deploy sanity checks automatically revert broken builds without manual intervention.

Does this smoke testing tool support Playwright, k6, and pytest for API and web service checks?

Cross-platform support includes pre-configured testing patterns for Playwright, k6, pytest, .NET, Spring Boot, and shell-based curl or sql probes. These patterns validate web, API, and backend services across any tech stack.

What is the difference between CI pipeline gating and continuous synthetic monitoring for smoke tests?

CI pipeline gating runs smoke tests as a post-deploy verification step to block broken releases, while continuous synthetic monitoring re-runs the same five critical checks every one to five minutes in production to detect ongoing failures.

How fast do post-deploy sanity checks need to run before they block the deployment pipeline?

Post-deploy sanity checks must complete in under two minutes to prevent pipeline bottlenecks. The suite runs parallel-safe, no-retry probes to instantly validate critical paths and trigger automated rollback if failures occur.