ui-review

Name: ui-review
Availability: InStock
Author: jvm-skills

Runs Playwright tests and captures screenshots to validate visual UI correctness.

135|25|Updated Feb 20, 2026

Search Tags:#screenshots #playwright #visual-testing #ui-review #ui-tests #web-ux

Ready to run

npx skills add https://github.com/jvm-skills/jvm-skills --skill ui-review-jvm-skills

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-review
Source: https://github.com/jvm-skills/jvm-skills/tree/main/.junie/skills/ui-review
Command: npx skills add https://github.com/jvm-skills/jvm-skills --skill ui-review-jvm-skills

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires test.

What problem does it solve?

UI regressions and visual inconsistencies slip into applications over time. This Skill helps verify UI/UX by automatically running Playwright tests and reviewing screenshots to ensure pages render correctly and flows remain intact.

Core Features & Use Cases

Run Playwright tests to generate fresh screenshots for target pages or components.
Review screenshots to validate layout, visuals, and user flows across the UI.
Use case: after implementing UI changes, fixing visual bugs, or validating an existing page against design specs.

Quick Start

Run the Playwright UI tests and review the generated screenshots to confirm the page looks correct.

Frequently Asked Questions about ui-review

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

FAQPage Schema

How do I automate visual testing for UI changes using Playwright?▼

Automate visual testing by executing Playwright tests to capture fresh screenshots, then review them to validate layout and visual correctness. This workflow verifies UI changes, bug fixes, and design reviews across web pages and components.

What is automated UI review and when do I need it for web pages?▼

Automated UI review is the process of running tests and checking screenshots to catch visual inconsistencies. You need it when implementing UI changes, fixing visual bugs, or validating existing pages against design specs to prevent regressions.

Do I need existing Playwright test suites to run automated UI checks?▼

Yes, you need existing Playwright test suites and a screenshot-review workflow described in references/project.md. These prerequisites provide the test execution environment and capture the screenshots required to validate visual correctness.

How do I verify user flows and layouts remain intact after a bug fix?▼

Verify user flows by running Playwright UI tests and reviewing the generated screenshots. This confirms the page looks correct and validates that layouts, visuals, and interactive flows remain intact after bug fixes.

What's the best way to catch UI regressions and visual inconsistencies in web components?▼

The best way to catch UI regressions is automating Playwright checks to generate screenshots of target pages or components. Reviewing these screenshots validates visual correctness and ensures rendering remains consistent over time.

Why does my UI review workflow require a project markdown reference file?▼

Your UI review workflow requires references/project.md because it describes the specific Playwright test suites and screenshot review steps needed. This file defines the custom workflow required to validate visual correctness for your project.