CDPWave Debugging

Debug browser automation via Chrome DevTools Protocol with breakpoints and heap snapshots.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/MathiasPaulenko/ai-toolkit --skill cdpwave-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CDPWave Debugging
Source: https://github.com/MathiasPaulenko/ai-toolkit/tree/main/skills/cdpwave-debugging
Command: npx skills add https://github.com/MathiasPaulenko/ai-toolkit --skill cdpwave-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cdpwave, and includes references (resource) and assets (resource) components.

What problem does it solve?

This skill addresses the complexity of debugging automated browser sessions by providing deep access to the Chrome DevTools Protocol for real-time inspection and performance profiling.

Core Features & Use Cases

  • Deep Debugging: Set conditional breakpoints, step through JavaScript execution, and inspect scope chains during automated tests.
  • Performance & Memory Analysis: Capture CPU profiles to identify bottlenecks and take heap snapshots to detect memory leaks.
  • Use Case: When an automated test fails intermittently due to a memory leak or a performance regression, use this skill to capture a heap snapshot and CPU profile to pinpoint the exact function causing the issue.

Quick Start

Use the cdpwave debugging skill to set a conditional breakpoint on line 42 of the target script and capture a heap snapshot for memory analysis.

Frequently Asked Questions about CDPWave Debugging

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

FAQPage Schema
How do I debug memory leaks in automated browser sessions?

Capture CPU profiles to identify bottlenecks in browser automation by executing Chrome DevTools Protocol commands to inspect real-time JavaScript execution and analyze scope chains for performance regressions.

How do I set conditional breakpoints during browser automation testing?

You can set conditional breakpoints during browser testing by using the Chrome DevTools Protocol to step through JavaScript execution and inspect scope chains within an active remote debugging session.

Do I need an active remote debugging session to capture CPU profiles and heap snapshots?

Yes, capturing CPU profiles and heap snapshots requires an active browser session with remote debugging enabled, along with the cdpwave dependency, to execute Chrome DevTools Protocol commands.

What is the best way to analyze performance bottlenecks in automated browser tests?

The best way to analyze performance bottlenecks is to capture CPU profiles and heap snapshots using the Chrome DevTools Protocol, allowing you to inspect real-time execution and resolve regressions.

Why does my automated browser test fail intermittently, and how can I diagnose it?

Intermittent test failures often stem from memory leaks or performance regressions, which you can diagnose by taking heap snapshots and capturing CPU profiles to isolate the problematic functions.