browser-qa

Drive Chrome DevTools to validate UI changes and generate pass/fail reports.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Coignite-ApS/businesslogic --skill browser-qa-coignite-aps
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-qa
Source: https://github.com/Coignite-ApS/businesslogic/tree/main/.claude/skills/browser-qa
Command: npx skills add https://github.com/Coignite-ApS/businesslogic --skill browser-qa-coignite-aps

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser QA agents verify UI changes by driving a real browser via Chrome DevTools MCP, capturing console errors, network activity, screenshots, and evidence-rich reports to ensure UI stability.

Core Features & Use Cases

  • Navigate pages, inspect elements, and interact with the UI through DevTools MCP commands.
  • Validate console messages, monitor network requests, and produce screenshot evidence for regression testing.
  • Generate structured pass/fail reports with traces and evidence for release validation.

Quick Start

Start a browser QA run against the target UI page and generate a verification report.

Frequently Asked Questions about browser-qa

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

FAQPage Schema
How do I automate browser QA checks for UI changes using Chrome DevTools?

Capture UI regression evidence by driving Chrome DevTools to inspect elements, monitor console messages, and track network activity. The Skill generates structured pass/fail reports with screenshots and traces, providing visual QA evidence for release validation.

Can I validate console errors and network requests during web application regression testing?

Validate console errors and network requests during regression testing by automating Chrome DevTools protocol commands. The Skill monitors network activity and console messages across pages, capturing screenshot evidence to ensure UI stability.

Do I need a Chrome DevTools protocol bridge to run automated browser testing?

A Chrome DevTools protocol bridge is required to execute MCP commands for navigation, interaction, and snapshot capture. Access to this bridge enables the Skill to drive the browser and generate structured pass/fail verification reports.

What is the best way to generate pass/fail reports with screenshots for release validation?

Generate pass/fail reports with screenshots by running automated Chrome DevTools checks against target UI pages. The Skill outputs structured verification reports containing traces, network data, and visual evidence for release validation.

Does browser automation for visual QA support interaction and snapshot capture across multiple pages?

Browser automation for visual QA supports interaction and snapshot capture across multiple pages via MCP commands. It navigates pages, inspects elements, interacts with the UI, and captures comprehensive evidence for regression testing.