skills.rest
DanielSuo117
DanielSuo117COMMUNITY
Explore all skills by this author →
GitHub

quick-debug

Diagnose UI test failures with in-page, login-free debugging.

176|2|Updated May 21, 2026
Search Tags:#automation#debugging#playwright#timeout#locator#in-page#is_page_loaded
One-click install
npx skills add https://github.com/DanielSuo117/velocitai --skill quick-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quick-debug
Source: https://github.com/DanielSuo117/velocitai/tree/main/zh/skills/quick-debug
Command: npx skills add https://github.com/DanielSuo117/velocitai --skill quick-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly diagnose and fix UI test failures by jumping directly to the failing page without a full login or rerun, enabling on-the-spot debugging.

Core Features & Use Cases

  • In-page DOM exploration via existing token-based bypass to inspect failing areas.
  • Integrated decision tree to classify issues into locator, timeout, assertion, or page-structure changes and trigger the appropriate remediation skill.
  • In-place verification of fixes using the current browser session, with guidance to re-run the full test after validation.

Quick Start

Run this skill on the failing test to immediately navigate to the problem page and begin on-site debugging.

Frequently Asked Questions about quick-debug

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

FAQPage Schema
How do I debug a Playwright test failure without rerunning the entire suite?▼

You can use in-page debugging to jump directly to the failing page without a full login or rerun. It enables on-the-spot DOM exploration to diagnose locator errors, timeouts, and assertion mismatches quickly.

What is the best way to diagnose Playwright locator errors and timeout failures?▼

An integrated decision tree classifies failures into locator, timeout, assertion, or page-structure categories. It then triggers the appropriate remediation skill to inspect the failing DOM area and validate the fix in-place.

Can I inspect a failing page's DOM structure without logging in during test debugging?▼

Yes, in-page debugging uses an existing token-based bypass to navigate directly to the problem page. This login-free approach enables immediate DOM exploration to identify root causes when page structure changes.

Does in-page debugging work with agent-browser for DOM exploration?▼

Yes, in-page debugging supports integration with agent-browser for DOM exploration. It also coordinates with locator-replacer, wait-strategy, and page-load-assertion skills to validate fixes in-place.

When should I run a full test suite after applying an in-page debug fix?▼

You should re-run the full test after validating your fix in the current browser session. In-place verification confirms the immediate targeted fix, but a complete rerun ensures overall suite stability.

Related Skills

Explore More Software Engineering Skills→
Prohao42Prohao42
120

authbypass-authentication-flaws

Identify and bypass authentication flaws in web applications.

Community
Advanced
loopyardloopyard
21

fix-bug

Reproduce bugs in Elixir/Mix projects using a test-first workflow.

Official
Intermediate
githubgithub
37.6k

webapp-testing

Automate browser-based testing of local web applications with Playwright.

Official
Intermediate
AbhiRKeesaraAbhiRKeesara

debugging-troubleshooting

Diagnose flaky Playwright tests using Inspector, trace viewer, and video analysis.

Community
Intermediate