AGENT SKILL

run-smoke-tests

Run Playwright smoke tests, debug failures, and verify fixes

License 许可
MIT
最近更新
2026-10-26
Stars
★ 0
Forks
0

01 前言 Front Matter

name
run-smoke-tests
description
Run Playwright smoke tests, debug failures, and verify fixes

03 SKILL.md 正文

Run smoke tests

Trigger

Need end-to-end smoke verification before or after changes.

Workflow

  1. Build prerequisites for the target app.
  2. Run the relevant smoke suite or a focused test file.
  3. If failing, inspect traces/logs and isolate the root cause.
  4. Apply a minimal fix and rerun until stable.

Example Commands

# Run full smoke suite
npm run smoketest

# Run a specific smoke test file
npm run smoketest -- path/to/test.spec.ts

# Faster iteration when build artifacts are ready
npm run smoketest-no-compile -- path/to/test.spec.ts

Guardrails

  • Prefer deterministic waits and assertions over brittle timeouts.
  • Re-run passing fixes to reduce flaky false positives.
  • Quarantine tests only when explicitly requested and documented.

Output

  • Test results summary
  • Root cause and fix
  • Remaining flake risk (if any)

04 同仓库更多 Skills

noodlemind
noodlemind/pstack-plugin

why

Use for 'why does X work this way', 'why we picked Y', design rationale, regressions, postmortems, or data-backed thresholds. Discovers available MCPs and queries each evidence category (source control, issue tracker, long-form docs, real-time chat, infrastructure observability, error tracking, product analytics warehouse) in parallel, then returns a cited read on decisions and tradeoffs. Use how for runtime behavior.

★ 0
noodlemind
noodlemind/pstack-plugin

unslop

Cut AI tells from any writing. Must always apply.

★ 0
noodlemind
noodlemind/pstack-plugin

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

★ 0
noodlemind
noodlemind/pstack-plugin

technical-writing

Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.

★ 0
noodlemind
noodlemind/pstack-plugin

teach

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

★ 0
noodlemind
noodlemind/pstack-plugin

tdd

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

★ 0