What problem does it solve?
Visual-validate detects visual regressions introduced by frontend pull requests by capturing route screenshots and performing automated visual analysis so teams can catch layout, text, and responsiveness issues before merging.
Core Features & Use Cases
- Captures screenshots for all routes affected by a PR across mobile, tablet, and desktop breakpoints.
- Maps changed frontend files to routes using the project's visual-helpers and creates a dynamic Playwright spec to exercise those routes.
- Analyzes screenshots with Claude Vision against a checklist (layout, text legibility, spacing, responsiveness, elements visibility, accentuation, states, colors) and categorizes issues by severity.
- Generates a REPORT.md summarizing routes tested, screenshots, and detailed actionable findings for QA and reviewers.
- Use case: Run as a pre-merge visual QA step when a PR modifies pages or components (.tsx, .css) to require visual approval.
Quick Start
Run the visual-validate workflow specifying the PR number to capture screenshots, analyze them with Claude Vision, and generate a REPORT.md.