regression-web-visual

Detects visual changes between two website states using matched screenshots and pixel diffs.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/celikgo/webmobai --skill regression-web-visual-celikgo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: regression-web-visual
Source: https://github.com/celikgo/webmobai/tree/main/.claude/skills/regression-web-visual
Command: npx skills add https://github.com/celikgo/webmobai --skill regression-web-visual-celikgo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deploys and redesigns can silently change how pages look, and manual before-and-after checking across many pages and breakpoints is slow and error-prone. This Skill captures matched screenshots of a baseline site and a current site, flags pages where structure or content changed, and optionally runs pixel-perfect diffs so regressions surface before users do. ## Core Features & Use Cases - Structural comparison: Captures full-page screenshots at matched URL paths and breakpoints, then flags changes in titles, heading counts, body text length, console errors, and broken images. - Pixel-perfect diffing: Uses pixelmatch-based snapshots with configurable thresholds, producing baseline, actual, and diff PNGs that highlight exactly which pixels changed. - Baseline versioning and rollback: Every baseline overwrite archives the previous image (up to 5 versions), so a wrongly accepted baseline can be listed and restored. - AI diff narration: Optionally turns a baseline/actual/diff PNG triple into a plain-English change list with a severity rating via a Claude API call. - Use Case: Before deploying, compare staging against production across your top five pages at desktop, tablet, and mobile widths, then review the flagged screenshot pairs and the HTML report. ## Quick Start Ask the AI to visually compare https://staging.example.com against https://example.com for the homepage, pricing, and signup pages across desktop and mobile breakpoints.

Frequently Asked Questions about regression-web-visual

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

FAQPage Schema
How do I run a visual regression test between staging and production?▼

Provide the baseline URL, current URL, page paths, and breakpoints. The Skill captures full-page screenshots of each path on both sides, compares titles, headings, text length, and errors, then generates an HTML report with flagged pages for manual review.

How to do pixel-perfect screenshot comparison in Playwright?▼

Use the webmobai_visual_snapshot tool with a snapshot name and a persistent baseline_dir. The first call writes the baseline; later calls run pixelmatch and produce .actual.png and .diff.png files when pixels differ beyond the configured threshold.

Can visual regression testing work on pages behind a login?▼

Yes, but both sides need the same authenticated state. Capture a storageState session file once and pass it to webmobai_launch_browser for both the baseline and current runs, otherwise every page appears changed due to login redirects.

Why does my visual snapshot keep saying baseline created instead of pass or fail?▼

The default baseline_dir resolves to a fresh temp directory each session, so every run writes a first-run baseline. Pass an explicit, persistent repo-relative baseline_dir so baselines survive across sessions and comparisons can occur.

How do I roll back a wrongly accepted visual baseline?▼

Call webmobai_visual_baseline_list_versions with the snapshot name and baseline_dir to see archived timestamps, then call webmobai_visual_baseline_restore_version with the chosen timestamp. Only the five most recent versions are retained.

What are the limitations of structural screenshot comparison?▼

Structural heuristics catch content and DOM changes but miss pure visual changes like color, spacing, or font shifts. For pixel-level detection, layer in webmobai_visual_snapshot on key elements, or use Percy or Chromatic for hosted team review.