Individual skill
visual-diff
Visual Regression Testing — screenshot comparison before and after changes. Use when user wants to check for visual regressions, compare UI changes, or verify CSS/layout changes didn't break anything.
skills/visual-diff/SKILL.md
Source commit ed232cba00040a3a8294aff08d14a0053cb8a0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 123
- Repository last updated
- Jul 8, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai Repository topic
- claude Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- code-review Repository topic
- developer-tools Repository topic
- indie-hackers Repository topic
- lighthouse Repository topic
- performance Repository topic
- playwright Repository topic
- design Derived category
- testing Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,242 bytes
Read excerpt
# Visual Regression Testing
Automated screenshot comparison using Playwright. Catch visual bugs before they ship.
## Process
### Phase 1: Determine Test Scope
Ask the user:
1. **What URL(s) to test?** (localhost, staging, or production)
2. **What changed?** (CSS update, component refactor, dependency upgrade, etc.)
If the user already described what changed, skip asking.
