File contents Visual Regression Tester
When to activate
User runs /test-visual-regression or requests visual regression testing to detect unintended style changes.
When NOT to use
Responsive design testing (use /test-responsive instead)
Performance profiling (use /profile-performance instead)
Accessibility reviews (use /review-a11y instead)
Instructions
Establish baseline snapshots
Capture current visual state (Chromatic, Percy, or local snapshots)
Generate snapshots for all component variants
Store baseline for comparison
Document baseline creation date and environment
Implement snapshot capture
Use Storybook addon (Chromatic, Percy) or Jest snapshots
Capture at consistent viewport size (1280x1024 standard)
Include hover, focus, active states
Capture light and dark modes (if supported)
Run visual regression test
Generate new snapshots after code change
Compare new snapshots to baseline
Identify pixel-level differences
Flag unintended changes (colors, spacing, fonts, etc.)
Triage visual changes
Intentional: Document approved changes (new design, refactor)
Unintended: Identify root cause (CSS, component change, dependency update)
Edge cases: Unexpected rendering in specific browsers/devices
Report findings
Before/after visual comparison
List of changed components
Impact assessment (user-visible, critical, cosmetic)
Root cause analysis for each change
Approve or reject changes
Approve intentional visual changes with justification
Reject unintended regressions
Require fix before merge
Update baseline for approved changes
Example
User: "Check for visual regressions after updating Button styles."
Response:
Changed components: 3 (Button primary, Button secondary, ButtonGroup)
Intentional changes detected: Button padding increased from 8px to 12px
Unintended regressions: Button outline color changed from gray to blue (unexpected)
Root cause: Removed .button:focus { color: blue } CSS line
Fix: Restore focus color CSS, re-snapshot
Impact: High (focus state critical for accessibility)
1 --- 2 name: visual-regression-tester 3 description: Visual Regression Tester 4 metadata: 5 source: https://skillmd.com/skills/uitbreidenos/visual-regression-tester 6 --- 7 # Visual Regression Tester 8 9 ## When to activate 10 11 User runs `/test-visual-regression` or requests visual regression testing to detect unintended style changes. 12 13 ## When NOT to use 14 15 - Responsive design testing (use `/test-responsive` instead) 16 - Performance profiling (use `/profile-performance` instead) 17 - Accessibility reviews (use `/review-a11y` instead) 18 19 ## Instructions 20 21 1. **Establish baseline snapshots** 22 - Capture current visual state (Chromatic, Percy, or local snapshots) 23 - Generate snapshots for all component variants 24 - Store baseline for comparison 25 - Document baseline creation date and environment 26 27 2. **Implement snapshot capture** 28 - Use Storybook addon (Chromatic, Percy) or Jest snapshots 29 - Capture at consistent viewport size (1280x1024 standard) 30 - Include hover, focus, active states 31 - Capture light and dark modes (if supported) 32 33 3. **Run visual regression test** 34 - Generate new snapshots after code change 35 - Compare new snapshots to baseline 36 - Identify pixel-level differences 37 - Flag unintended changes (colors, spacing, fonts, etc.) 38 39 4. **Triage visual changes** 40 - **Intentional:** Document approved changes (new design, refactor) 41 - **Unintended:** Identify root cause (CSS, component change, dependency update) 42 - **Edge cases:** Unexpected rendering in specific browsers/devices 43 44 5. **Report findings** 45 - Before/after visual comparison 46 - List of changed components 47 - Impact assessment (user-visible, critical, cosmetic) 48 - Root cause analysis for each change 49 50 6. **Approve or reject changes** 51 - Approve intentional visual changes with justification 52 - Reject unintended regressions 53 - Require fix before merge 54 - Update baseline for approved changes 55 56 ## Example 57 58 User: "Check for visual regressions after updating Button styles." 59 60 Response: 61 - **Changed components:** 3 (Button primary, Button secondary, ButtonGroup) 62 - **Intentional changes detected:** Button padding increased from 8px to 12px 63 - **Unintended regressions:** Button outline color changed from gray to blue (unexpected) 64 - **Root cause:** Removed `.button:focus { color: blue }` CSS line 65 - **Fix:** Restore focus color CSS, re-snapshot 66 - **Impact:** High (focus state critical for accessibility)
UitbreidenOS/UitKit commit fbf0ad01a1
Frequently asked questions How do I install the Visual Regression Tester skill? Run npx get-skill add uitbreidenos/visual-regression-tester in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Visual Regression Tester skill do? Visual Regression Tester It is listed under Coding & Dev Tools on SkillMD.
Is Visual Regression Tester safe to use? This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Visual Regression Tester? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Visual Regression Tester free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Visual Regression Tester? UitbreidenOS (@uitbreidenos) published this skill. Their other Agent Skills are listed on their SkillMD profile.