visual-snapshot-check

Capture full-page screenshots with Playwright and compare them against baselines.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/eboody/eran.codes --skill visual-snapshot-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: visual-snapshot-check
Source: https://github.com/eboody/eran.codes/tree/main/archive/skills/visual-snapshot-check
Command: npx skills add https://github.com/eboody/eran.codes --skill visual-snapshot-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that visual and UI changes in your application's front-end components and styling are detected and validated against established baselines, preventing unintended visual regressions.

Core Features & Use Cases

  • Automated Screenshot Capture: Generates full-page screenshots of web pages using Playwright.
  • Baseline Comparison: Compares newly captured screenshots against a set of predefined baseline images to identify visual differences.
  • Use Case: After updating CSS or Maud components, run this skill to automatically verify that the UI still looks as expected and that no visual bugs have been introduced.

Quick Start

Run the visual snapshot check script to capture and compare UI screenshots against baselines.

Frequently Asked Questions about visual-snapshot-check

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

FAQPage Schema
How do I automate visual regression testing with Playwright?

Playwright visual regression testing automates full-page screenshot capture and compares current captures against predefined baseline images to detect UI changes. This skill executes those Playwright baseline checks to validate UI integrity and prevent unintended visual regressions in Maud views and CSS.

What is UI visual regression testing and when do I need it?

UI visual regression testing is the process of comparing current webpage screenshots against established baselines to detect unintended visual changes. You need it after updating CSS or Maud components to verify that your UI still looks as expected and no visual bugs have been introduced.

How do I update screenshot baselines when visual changes are intentional?

To update screenshot baselines for intentional visual changes, run the skill with the VISUAL_UPDATE_BASELINE environment variable set to 1. This automated baseline refreshing process replaces established baseline images with your newly captured Playwright screenshots.

Does this visual snapshot check tool support Maud views and CSS components?

Yes, visual snapshot check specifically supports Maud views and CSS components by validating UI integrity through full-page screenshot comparisons. It detects visual and UI changes in your front-end styling to ensure consistency across updates.

What is the best way to detect CSS regressions in frontend components?

The best way to detect CSS regressions is to run automated Playwright full-page screenshot captures and compare them against predefined baseline images. This approach validates visual consistency by identifying unintended UI differences introduced during component updates.

Why does my visual regression test fail after updating frontend styling?

Visual regression tests fail after updating frontend styling because the newly captured screenshots differ from the established baseline images. If the visual changes to your CSS or Maud views are intentional, refresh the baselines using VISUAL_UPDATE_BASELINE=1.