How do I trigger a smoke test using this skill?

You can initiate a smoke test by asking Claude to 'run a smoke test' or by using the shorthand command '/st' or '/smoke-test'.

What parts of my application does this skill test?

The skill typically executes a pre-defined suite that covers system health, user authentication, core application features, and critical external integrations.

How long do the tests usually take?

Following best practices, the smoke test suite is designed to be rapid, typically completing in under 5 minutes to provide immediate feedback.

Can I integrate this into my CI/CD pipeline?

Yes, integrating these smoke tests into your CI/CD pipeline is recommended for automated post-deployment verification and continuous reliability.

When is the best time to use the Smoke Test Runner?

It is best used immediately after a deployment, following an upgrade, or after making significant configuration changes to ensure the application is still operational.

Automated Smoke Test Runner

Name: Automated Smoke Test Runner
Author: jeremylongshore

byjeremylongshore

•

883

Security & Testing

Executes rapid application verification suites to ensure critical functionality and system health after code changes or deployments.

About

The Automated Smoke Test Runner skill empowers Claude to perform high-level verification of your application's most critical paths. By executing pre-defined test suites covering authentication, core features, and external integrations, it provides a quick pass/fail assessment that identifies major regressions early. This skill is particularly valuable immediately following deployments, infrastructure upgrades, or database configuration changes, allowing developers to confirm operational status within minutes without manual intervention.

Key Features

System health monitoring and validation
Detailed reporting on test suite execution results
883 GitHub stars
Automated authentication and integration checks
Quick command triggers via 'smoke test' or 'st'
Rapid pass/fail feedback for critical user flows

Use Cases

Verifying application stability immediately after a production deployment
Sanity-checking core features during the development and CI/CD lifecycle
Validating system health after database or environment configuration updates

About

Key Features

System health monitoring and validation
Detailed reporting on test suite execution results
883 GitHub stars
Automated authentication and integration checks
Quick command triggers via 'smoke test' or 'st'
Rapid pass/fail feedback for critical user flows

Use Cases

Verifying application stability immediately after a production deployment
Sanity-checking core features during the development and CI/CD lifecycle
Validating system health after database or environment configuration updates