run-smoke-tests

Run Playwright smoke tests and rerun until stable with traces and logs.

Updated May 22, 2026
One-click install
npx skills add https://github.com/paulbrittain/claude-team-kit --skill run-smoke-tests-paulbrittain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: run-smoke-tests
Source: https://github.com/paulbrittain/claude-team-kit/tree/main/skills/run-smoke-tests
Command: npx skills add https://github.com/paulbrittain/claude-team-kit --skill run-smoke-tests-paulbrittain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch end-to-end regressions early by running reliable smoke tests and quickly turning failures into actionable fixes.

Core Features & Use Cases

  • Build-aware smoke verification: Prepares prerequisites for the target app before running tests.
  • Focused and iterative reruns: Runs a relevant smoke suite or a specific test file, then reruns after applying minimal fixes.
  • Failure triage with traces/logs: Inspects traces and logs to isolate the root cause and reduce flake risk.

Quick Start

Ask the Skill to run the full Playwright smoke suite and debug any failures until they become stable.

Frequently Asked Questions about run-smoke-tests

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

FAQPage Schema
How do I run Playwright smoke tests to verify critical workflows before a release?

Playwright smoke tests validate critical workflows by building prerequisites, running the relevant test suite, and iteratively rerunning failures until the suite becomes stable for release gating.

What is the best way to triage failing end-to-end tests and reduce flake risk?

Triage failing end-to-end tests by inspecting collected traces and logs to isolate the root cause, applying minimal fixes, and rerunning the specific test file until the failures are resolved and flake risk is reduced.

Does this smoke testing approach work for post-merge verification in CI/CD?

Yes, this smoke testing approach works for post-merge verification in CI/CD by providing deterministic execution that builds prerequisites, runs targeted Playwright checks, and collects failure traces for quick debugging.

Can I run a specific Playwright test file instead of the full smoke suite?

Yes, you can run a specific Playwright test file instead of the full smoke suite, allowing you to focus on targeted debugging of failing end-to-end test files and iteratively rerun them after applying minimal fixes.

Why does my Playwright smoke suite fail during CI release validation?

Your Playwright smoke suite may fail during CI release validation due to missing application prerequisites, unstable workflows, or end-to-end regressions, which you can isolate by collecting traces and logs to debug the root cause.