skills.rest
h-4vok
h-4vokCOMMUNITY
Explore all skills by this author →
GitHub

smoke-investigation

Diagnose Playwright smoke failures and runtime-visible regressions in diagram-tours.

Updated Mar 11, 2026
Search Tags:#debugging#diagnostics#playwright#smoke-tests#regressions#diagram-tours
One-click install
npx skills add https://github.com/h-4vok/diagram-tours --skill smoke-investigation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: smoke-investigation
Source: https://github.com/h-4vok/diagram-tours/tree/main/.agents/skills/smoke-investigation
Command: npx skills add https://github.com/h-4vok/diagram-tours --skill smoke-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate Playwright smoke failures and runtime-visible regressions in diagram-tours. Use when bun run smoke fails or when debugging viewport, browse, minimap, theme, startup modes, deep links, or other browser-visible flows.

Core Features & Use Cases

  • Identify failing smoke tests in Playwright integrated with diagram-tours.
  • Reproduce the smallest failing case and categorize it as product bug, behavior change, or brittle assertion.
  • Provide actionable diagnostics and guidance for fixes in test suites and UI flows.

Quick Start

Run bun run smoke to reproduce the smallest failing case and start your investigation.

Frequently Asked Questions about smoke-investigation

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

FAQPage Schema
How do I debug Playwright smoke test failures in diagram-tours?▼

Debug Playwright smoke failures by reproducing the smallest failing case to identify whether the issue is a product bug, a behavior change, or a brittle assertion in viewport or browse flows.

Why does my Playwright smoke test fail during viewport or minimap rendering?▼

Playwright smoke tests fail during viewport or minimap rendering due to runtime-visible regressions in browser flows, which require isolating the smallest failing case to diagnose as a product bug or brittle assertion.

What is the best way to troubleshoot Playwright runtime regressions in browser-visible flows?▼

The best way to troubleshoot Playwright runtime regressions is to reproduce the smallest failing case and determine if the issue stems from a product bug, a behavior change, or a brittle assertion.

Can I use this approach to diagnose deep link and startup mode regressions in Playwright?▼

Yes, you can diagnose deep link and startup mode regressions by investigating runtime-visible failures in Playwright smoke tests and categorizing them as product bugs or behavior changes requiring spec updates.

How do I know if a Playwright smoke failure is a brittle assertion or a product bug?▼

Identify a brittle assertion versus a product bug by reproducing the smallest failing case during the smoke investigation and evaluating whether the runtime behavior change requires a spec update or an actual code fix.

Do I need bun run smoke to investigate Playwright test regressions?▼

Yes, you need to run bun run smoke to reproduce the smallest failing case and start investigating whether the Playwright test regression is a product bug, behavior change, or brittle assertion.

Related Skills

Explore More Software Engineering Skills→
v1-iov1-io
6

fix-tests

Diagnose failing test outputs and apply minimal fixes across the codebase.

Official
Advanced
Chai-UnChai-Un

fix

Fix lint errors and formatting issues using yarn, prettier, and linc.

Community
Intermediate
semicolon-devteamsemicolon-devteam

e2e-test

Automate Playwright end-to-end tests to validate runtime browser behavior.

Official
Advanced
jaimedhenriquesjaimedhenriques

playwright

Automate real-browser navigation, form filling, and screenshots via Playwright CLI.

Community
Intermediate