visual-qa

Inspect the running web app in Chrome and report visual regressions, layout issues, console errors, and network failures.

3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/gwpjp/Web3-Claude --skill visual-qa-gwpjp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visual-qa
Source: https://github.com/gwpjp/Web3-Claude/tree/main/.claude/skills/visual-qa
Command: npx skills add https://github.com/gwpjp/Web3-Claude --skill visual-qa-gwpjp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the visual QA process for UI changes by inspecting the running app in Chrome, taking screenshots, and reporting layout issues, console errors, and network failures.

Core Features & Use Cases

  • Visual inspection: Open the app in Chrome, navigate routes, and verify the rendered visuals against expected baselines.
  • Issue detection: Identify layout problems, missing assets, and console warnings/errors after UI changes.
  • Report generation: Compile findings into a coherent narrative report for developers and designers.

Quick Start

Start the visual QA inspector after UI changes, ensure a Chrome tab is available, and run the agent to validate the latest rendering results.

Frequently Asked Questions about visual-qa

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

FAQPage Schema
How do I automate visual QA testing for UI changes in Chrome?

To automate visual QA testing for UI changes, this skill inspects your running web app in Chrome, captures screenshots, and reports visual regressions. It navigates predefined routes to verify rendering consistency and detect layout issues after updates.

Can I detect console and network errors automatically after a UI update?

Yes, you can detect console and network errors automatically after a UI update. The visual QA process profiles your active Chrome tab to identify JavaScript console warnings, runtime errors, and network failures alongside visual layout regressions.

What is the best way to perform a layout-diff comparison on a running web app?

The best way to perform a layout-diff comparison on a running web app is by capturing screenshots across predefined routes and comparing rendered visuals against expected baselines. This skill orchestrates sub-agents to validate rendering consistency and flag layout problems.

Does this visual regression testing work with React DevTools and Lighthouse?

Yes, visual regression testing works with React DevTools and Lighthouse. The skill orchestrates sub-agents for Chrome DevTools profiling, React DevTools, and Lighthouse to analyze code and report visual issues, console errors, and network failures.

Do I need a predefined route map to run UI testing on my web application?

Yes, you need a predefined route map to run UI testing on your web application. The visual QA inspection relies on this route map to navigate your app systematically, ensuring all targeted pages are captured and validated for rendering consistency.

Why is my visual QA inspection not capturing screenshots of all pages?

Your visual QA inspection may not capture screenshots of all pages if there is no active Chrome tab available or the predefined route map is incomplete. The skill requires a running web app and an accessible Chrome instance to navigate routes and verify rendered visuals.