running-smoke-tests
About
This skill runs smoke tests to verify critical application functionality through pre-defined test suites. It checks system health, authentication, core features, and external integrations to ensure operational status. Use it after deployments, upgrades, or significant configuration changes by triggering with "smoke test" or "st".
Documentation
Overview
This skill enables Claude to quickly verify the critical functionality of an application by running a suite of smoke tests. It provides a fast pass/fail assessment, helping to identify potential issues early in the deployment process.
How It Works
- Initiate Smoke Test: The user requests a smoke test using the
/smoke-testor/stcommand. - Execute Test Suite: The skill executes the pre-defined suite of smoke tests, covering system health, authentication, core features, and external integrations.
- Report Results: The skill provides a summary of the test results, indicating whether the tests passed or failed.
When to Use This Skill
This skill activates when you need to:
- Verify application functionality after a deployment.
- Confirm system health after an upgrade.
- Sanity-check critical features after configuration changes.
Examples
Example 1: Post-Deployment Verification
User request: "Run a smoke test after deploying the new version."
The skill will:
- Execute the smoke test suite.
- Report the pass/fail status of each test, highlighting any failures in authentication or core feature validation.
Example 2: Configuration Change Validation
User request: "/st to validate the recent database configuration changes."
The skill will:
- Execute the smoke test suite.
- Report the results, specifically checking the system health and integration tests to ensure the database changes didn't introduce issues.
Best Practices
- Focus: Ensure smoke tests focus on the most critical user flows and system components.
- Speed: Keep the smoke test suite execution time under 5 minutes for rapid feedback.
- Integration: Integrate smoke tests into your CI/CD pipeline for automated post-deployment verification.
Integration
This skill can be used in conjunction with other deployment and monitoring tools to provide a comprehensive view of application health and stability. It works independently, requiring only the /smoke-test or /st command to initiate.
Quick Install
/plugin add https://github.com/jeremylongshore/claude-code-plugins-plus/tree/main/smoke-test-runnerCopy and paste this command in Claude Code to install this skill
GitHub 仓库
Related Skills
evaluating-llms-harness
TestingThis Claude Skill runs the lm-evaluation-harness to benchmark LLMs across 60+ standardized academic tasks like MMLU and GSM8K. It's designed for developers to compare model quality, track training progress, or report academic results. The tool supports various backends including HuggingFace and vLLM models.
langchain
MetaLangChain is a framework for building LLM applications using agents, chains, and RAG pipelines. It supports multiple LLM providers, offers 500+ integrations, and includes features like tool calling and memory management. Use it for rapid prototyping and deploying production systems like chatbots, autonomous agents, and question-answering services.
webapp-testing
TestingThis Claude Skill provides a Playwright-based toolkit for testing local web applications through Python scripts. It enables frontend verification, UI debugging, screenshot capture, and log viewing while managing server lifecycles. Use it for browser automation tasks but run scripts directly rather than reading their source code to avoid context pollution.
business-rule-documentation
MetaThis skill provides standardized templates for systematically documenting business logic and domain knowledge following Domain-Driven Design principles. It helps developers capture business rules, process flows, decision trees, and terminology glossaries to maintain consistency between requirements and implementation. Use it when documenting domain models, creating business rule repositories, or bridging communication between business and technical teams.