run-smoke-tests

Automate end-to-end smoke tests and diagnose failures with traces and logs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/namhoangg/agent-starter-kit --skill run-smoke-tests-namhoangg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-smoke-tests
Source: https://github.com/namhoangg/agent-starter-kit/tree/main/cursor/skills/run-smoke-tests
Command: npx skills add https://github.com/namhoangg/agent-starter-kit --skill run-smoke-tests-namhoangg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end smoke verification before or after changes to ensure stable builds of the target application.

Core Features & Use Cases

  • End-to-end smoke verification
  • Deterministic test execution for full suite or focused tests
  • Diagnostic workflow to inspect traces and apply fixes

Quick Start

Run the full smoke test suite after changes using npm run smoketest.

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 end-to-end smoke tests to verify application fixes?▼

End-to-end smoke tests verify application fixes by automating prerequisite building, running the smoke test suite, and isolating failures through deterministic execution to guide iterative fixes.

Can I run focused smoke tests instead of the full suite?▼

Focused smoke tests are supported alongside the full suite, allowing deterministic test execution that targets specific application areas to quickly verify changes without running everything.

How do I diagnose smoke test failures using traces and logs?▼

Diagnosing smoke test failures involves inspecting generated traces and logs to isolate failure points, enabling an iterative fix-and-test workflow that guides targeted application corrections.

Does this smoke testing workflow integrate with CI/CD pipelines?▼

Smoke testing workflows integrate with CI/CD pipelines to automate end-to-end verification before or after changes, ensuring stable builds through deterministic test execution during continuous delivery.

What is the best way to verify stable builds after code changes?▼

Verifying stable builds after code changes is best achieved by running automated end-to-end smoke tests that quickly validate fixes and ensure the target application remains functional.

Why are my Playwright smoke tests failing intermittently?▼

Intermittent Playwright smoke test failures can be resolved by applying deterministic test execution principles, using traces and logs to isolate flaky behavior, and running focused tests to pinpoint root causes.