browser-testing-with-devtools

Diagnoses browser runtime issues by inspecting live page behavior, console output, network activity, and rendered DOM state.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/alissonpef/copilot-agent-skills --skill browser-testing-with-devtools-alissonpef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-testing-with-devtools
Source: https://github.com/alissonpef/copilot-agent-skills/tree/main/.github/skills/browser-testing-with-devtools
Command: npx skills add https://github.com/alissonpef/copilot-agent-skills --skill browser-testing-with-devtools-alissonpef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you verify and debug what actually happens in the browser, instead of guessing from static code alone. It is designed to catch UI defects, runtime errors, network issues, accessibility gaps, and performance problems using real browser data.

Core Features & Use Cases

  • Visual verification: Compare screenshots before and after a change to confirm the page looks correct.
  • Runtime inspection: Read the live DOM, console output, accessibility tree, and computed styles to diagnose browser behavior.
  • Network and performance analysis: Inspect requests, responses, timing, and traces to find API failures or slow interactions.
  • Use case: A layout looks fine in code review but breaks at runtime on mobile; this Skill helps reproduce the issue, inspect the rendered page, and confirm the fix in the browser.

Quick Start

Use the browser-testing-with-devtools skill to inspect the current page, capture browser errors, and verify the fix with a live screenshot.

Frequently Asked Questions about browser-testing-with-devtools

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

FAQPage Schema
How do I debug browser runtime issues using Chrome DevTools?

To debug browser runtime issues with Chrome DevTools, you inspect live page behavior by capturing screenshots, reading console output, analyzing network activity, and inspecting the rendered DOM state to diagnose UI bugs and API failures.

What is the best way to diagnose UI styling regressions in a live browser session?

Diagnosing UI styling regressions in a live browser session involves inspecting the rendered DOM, reading computed styles, and comparing screenshots before and after a change to verify the visual output matches the expected layout.

How do I inspect network activity and performance traces for slow web applications?

You inspect network activity and performance traces for slow web applications by monitoring browser requests, responses, and timing data to identify API failures or slow interactions during real user interactions.

Can I check web accessibility issues using the browser accessibility tree?

Yes, you can check web accessibility issues by inspecting the live accessibility tree within Chrome DevTools to evaluate rendered DOM state and computed styles for gaps in real browser sessions.

Do I need Chrome DevTools MCP access to inspect console logs and JavaScript state?

Yes, you need Chrome DevTools MCP access to inspect console logs and perform read-only JavaScript state inspection, as it provides the necessary interface to capture runtime data, screenshots, and network traces.

Why does my layout look fine in code review but break at runtime on mobile?

A layout might break at runtime on mobile due to dynamic DOM rendering or computed style conflicts, which you can reproduce and diagnose by inspecting the live page behavior and capturing screenshots in a real browser session.