running-smoke-tests

Execute fast smoke tests validating critical functionality after deployment. Use when performing specialized testing. Trigger with phrases like "run smoke tests", "quick validation", or "test critical paths".

跳到安装

仓库: jeremylongshore/claude-code-plugins-plus-skills
最近来源活动: 2026年7月17日 22:18
检测到的 SKILL.md 语言: 英语
星标: 2,604
分支: 378

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill running-smoke-tests

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

文件资源管理器

4 个文件

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

clerk-core-workflow-a

Implement user sign-up and sign-in flows with Clerk. Use when building authentication UI, customizing sign-in experience, or implementing OAuth social login. Trigger with phrases like "clerk sign-in", "clerk sign-up", "clerk login flow", "clerk OAuth", "clerk social login".

2026-07-23

clerk-core-workflow-b

Implement session management and middleware with Clerk. Use when managing user sessions, configuring route protection, or implementing token refresh and custom JWT templates. Trigger with phrases like "clerk session", "clerk middleware", "clerk route protection", "clerk token", "clerk JWT".

2026-07-23

clerk-enterprise-rbac

Configure enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls. Trigger with phrases like "clerk SSO", "clerk RBAC", "clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".

2026-07-23

查看这个仓库的全部 Skills

Smoke Test Runner

Overview

Execute fast, high-confidence smoke tests that validate critical application functionality after deployment or build. Smoke tests verify that the application starts, core user flows work, and key integrations respond -- without running the full test suite.

Prerequisites

Application deployed and accessible at a known URL or running locally

HTTP client available (curl, wget, node-fetch, or Playwright)

List of critical endpoints and user flows to validate

Expected response codes and content patterns for each check

CI/CD pipeline hook for post-deployment validation

Instructions

Identify the critical paths that constitute a "working" application:

Health check endpoint returns 200 with expected body.
Homepage loads and contains key UI elements.
Authentication flow succeeds with test credentials.
Primary API endpoint returns valid data.
Database connection is active and responding.

Create a smoke test configuration listing each check:

URL or command to execute.
Expected HTTP status code (200, 301, etc.).
Response body pattern to match (substring or regex).
Maximum acceptable response time (e.g., 3 seconds).

Write the smoke test suite as a lightweight script or test file:

Use curl for HTTP checks or Playwright for browser-based checks.
Run checks sequentially for simplicity (parallel for speed if independent).
Fail fast on the first critical failure.
Log each check result with pass/fail, response time, and status code.

Implement timeout guards:

Set a global timeout of 60 seconds for the entire smoke suite.
Set per-check timeouts of 5-10 seconds.
Treat timeouts as failures, not retries.

Add deployment-gate integration:

On success: proceed with deployment promotion or traffic shifting.
On failure: trigger rollback and send alert notification.
Report results to CI/CD dashboard and Slack/Teams webhook.

Store smoke test results as CI artifacts for audit trail.

Schedule periodic smoke runs (every 5 minutes in production) as synthetic monitoring.

Output

Smoke test script (scripts/smoke-test.sh or tests/smoke.test.ts)

Smoke Test Runner

Overview

Prerequisites

Application deployed and accessible at a known URL or running locally

HTTP client available (curl, wget, node-fetch, or Playwright)

List of critical endpoints and user flows to validate

Expected response codes and content patterns for each check

CI/CD pipeline hook for post-deployment validation

Instructions

Identify the critical paths that constitute a "working" application:

Health check endpoint returns 200 with expected body.
Homepage loads and contains key UI elements.
Authentication flow succeeds with test credentials.
Primary API endpoint returns valid data.
Database connection is active and responding.

Create a smoke test configuration listing each check:

URL or command to execute.
Expected HTTP status code (200, 301, etc.).
Response body pattern to match (substring or regex).
Maximum acceptable response time (e.g., 3 seconds).

Write the smoke test suite as a lightweight script or test file:

Use curl for HTTP checks or Playwright for browser-based checks.
Run checks sequentially for simplicity (parallel for speed if independent).
Fail fast on the first critical failure.
Log each check result with pass/fail, response time, and status code.

Implement timeout guards:

Set a global timeout of 60 seconds for the entire smoke suite.
Set per-check timeouts of 5-10 seconds.
Treat timeouts as failures, not retries.

Add deployment-gate integration:

On success: proceed with deployment promotion or traffic shifting.
On failure: trigger rollback and send alert notification.
Report results to CI/CD dashboard and Slack/Teams webhook.

Store smoke test results as CI artifacts for audit trail.

Schedule periodic smoke runs (every 5 minutes in production) as synthetic monitoring.

Output

Smoke test script (scripts/smoke-test.sh or tests/smoke.test.ts)

name	running-smoke-tests
description	Execute fast smoke tests validating critical functionality after deployment. Use when performing specialized testing. Trigger with phrases like "run smoke tests", "quick validation", or "test critical paths".
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(test:smoke-*)
version	1.20.0
author	Jeremy Longshore <jeremy@intentsolutions.io>
license	MIT
tags	["testing","deployment","smoke-tests"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

name	running-smoke-tests
description	Execute fast smoke tests validating critical functionality after deployment. Use when performing specialized testing. Trigger with phrases like "run smoke tests", "quick validation", or "test critical paths".
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(test:smoke-*)
version	1.20.0
author	Jeremy Longshore <jeremy@intentsolutions.io>
license	MIT
tags	["testing","deployment","smoke-tests"]
compatibility	Designed for Claude Code, also compatible with Codex and OpenClaw

Error	Cause	Solution
Connection refused	Application not yet ready after deployment	Add a startup wait with exponential backoff (max 30 seconds) before running smoke tests
503 Service Unavailable	Application is starting or behind a load balancer draining	Retry with 2-second delay up to 3 times; check load balancer health check status
Unexpected redirect (301/302)	URL changed or SSL redirect not accounted for	Follow redirects with `curl -L`; update expected URLs in smoke config
Content mismatch	Page content changed but smoke test pattern is too specific	Use broad patterns (check for `<title>` or key element IDs, not exact text)
Timeout on database check	Database migration running or connection pool exhausted	Increase timeout for database checks; verify migration completed before smoke tests

running-smoke-tests

安装方式

检查来源文件

Smoke Test Runner

Overview

Prerequisites

Instructions

Output

Smoke Test Runner

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources

running-smoke-tests

来源信息

安装方式

检查来源文件

同仓库更多 Skills

同仓库更多 Skills

Smoke Test Runner

Overview

Prerequisites

Instructions

Output

Smoke Test Runner

Overview

Prerequisites

Instructions

Output

Error Handling

Examples

Resources