debugging-skill

Restarts browser sessions and walks user flows to capture console errors after code changes.

46|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/bitovi/vybit --skill debugging-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-skill
Source: https://github.com/bitovi/vybit/tree/main/.github/skills/debugging
Command: npx skills add https://github.com/bitovi/vybit --skill debugging-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers verify that their web application is free of runtime errors and warnings after any code update, ensuring a stable user experience.

Core Features & Use Cases

  • Browser Session Reset: Restart browser sessions to prevent stale state issues.
  • Full User Flow Testing: Walk through complete user interactions in the app.
  • Error Monitoring: Capture console errors, warnings, and exceptions during testing.
  • Use Case: When deploying new features, use this Skill to automatically validate the app runs without errors before proceeding with further testing or production.

Quick Start

Use this Skill to restart your test environment, navigate through key user flows, and check for errors without manual browser inspection.

Frequently Asked Questions about debugging-skill

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

FAQPage Schema
How do I automate UI testing to capture console errors after code changes?

You can automate UI testing to capture console errors by using Playwright to restart browser sessions, walk through user flows, and monitor the console for runtime errors and warnings, ensuring application stability after code changes.

What is the best way to clear stale browser state before running web application stability tests?

The best way to clear stale browser state is to automate a browser session reset, which restarts the environment and prevents stale state issues before walking through complete user interactions to check for runtime errors.

Does Playwright work with shadow DOM interactions when debugging frontend errors?

Yes, Playwright works with shadow DOM interactions to handle complex UI elements during automated error monitoring, allowing the tool to navigate deep user flows and capture frontend exceptions effectively.

Why should I monitor console warnings and exceptions during user flow testing?

You should monitor console warnings and exceptions during user flow testing to verify your web application is free of runtime errors after code updates, ensuring a stable user experience before proceeding to production.

What do I need to set up before validating web application stability with automated UI testing?

You need automation tools like Playwright configured in your test environment to handle browser session resets, shadow DOM interactions, and error monitoring before you can validate web application stability.