Our review
Captures before/after screenshots of two URLs or two images so UI changes can be compared visually.
Strengths
- Works with file://, http:// and https:// URLs, existing image paths, CSS selectors, and mobile, tablet or custom viewports
- Built-in pre-flight checks, including detection of Vercel deployment protection (401/403) before capturing
- The --markdown flag uploads images and produces a comparison table that can be appended to a GitHub PR via gh
- Explicit agent rules prevent side effects such as switching branches, stashing changes, or starting dev servers
Limitations
- Requires Node/npm plus a global install or npx run of the @vercel/before-and-after package
- Default image hosting is a public service (0x0.st), so sensitive internal screenshots may be exposed
- The 'before' state must be reachable at a separate URL; the agent asks for it rather than guessing
Use it when you need to visually compare a UI before and after a change and document the result in a pull request.
Not suitable for automated visual regression in CI or for authenticated pages that lack a bypass token.
Security analysis
CautionThe skill uses network operations, installs a package globally, uploads files to third-party services, and edits GitHub PR content, all for a legitimate visual comparison workflow. No destructive or exfiltration-oriented commands are present, but the upload and PR modification capabilities warrant caution.
- •Installs and executes a global npm package from the npm registry.
- •Uploads screenshot images to an external service (0x0.st by default) or GitHub Gist, which could expose sensitive UI content if used on private pages.
- •Can modify GitHub pull request bodies via gh pr edit.
- •Uses network requests (curl, vercel inspect) and Vercel CLI commands.
Examples
Take before and after screenshots of https://myapp.com/pricing (before) and http://localhost:3000/pricing (after).Compare the hero section on mobile: screenshot .hero-section on both https://staging.myapp.com and http://localhost:3000.Upload before.png and after.png as a markdown comparison and append it to the current pull request.name: before-and-after description: Captures before/after screenshots of web pages or elements for visual comparison. Use when user says "take before and after", "screenshot comparison", "visual diff", "PR screenshots", "compare old and new", or needs to document UI changes. Accepts two URLs (file://, http://, https://) or two image paths. allowed-tools:
- Bash(npx @vercel/before-and-after *)
- Bash(before-and-after *)
- Bash(which before-and-after)
- Bash(npm install -g @vercel/before-and-after)
- Bash(*/upload-and-copy.sh *)
- Bash(curl -s -o /dev/null -w *)
- Bash(gh pr view *)
- Bash(gh pr edit *)
- Bash(vercel inspect *)
- Bash(vercel whoami)
- Bash(which vercel)
- Bash(which gh)
Before-After Screenshot Skill
Package:
@vercel/before-and-afterNever usebefore-and-after(wrong package).
Agent Behavior Rules
DO NOT:
- Switch git branches, stash changes, start dev servers, or assume what "before" is
- Use
--fullunless user explicitly asks for full page / full scroll capture
DO:
- Use
--markdownwhen user wants PR integration or markdown output - Use
--mobile/--tabletif user mentions phone, mobile, tablet, responsive, etc. - Assume current state is After
- If user provides only one URL or says "PR screenshots" without URLs, ASK: "What URL should I use for the 'before' state? (production URL, preview deployment, or another local port)"
Execution Order (MUST follow)
- Pre-flight —
which before-and-after || npm install -g @vercel/before-and-after - Protection check — if
.vercel.appURL:curl -s -o /dev/null -w "%{http_code}" "<url>"(401/403 = protected) - Capture —
before-and-after "<before-url>" "<after-url>" - Upload —
./scripts/upload-and-copy.sh <before.png> <after.png> --markdown - PR integration — optionally
gh pr editto append markdown
Never skip steps 1-2.
Quick Reference
# Basic usage
before-and-after <before-url> <after-url>
# With selector
before-and-after url1 url2 ".hero-section"
# Different selectors for each
before-and-after url1 url2 ".old-card" ".new-card"
# Viewports
before-and-after url1 url2 --mobile # 375x812
before-and-after url1 url2 --tablet # 768x1024
before-and-after url1 url2 --full # full scroll
# From existing images
before-and-after before.png after.png --markdown
# Via npx (use full package name!)
npx @vercel/before-and-after url1 url2
| Flag | Description |
|------|-------------|
| -m, --mobile | Mobile viewport (375x812) |
| -t, --tablet | Tablet viewport (768x1024) |
| --size <WxH> | Custom viewport |
| -f, --full | Full scrollable page |
| -s, --selector | CSS selector to capture |
| -o, --output | Output directory (default: ~/Downloads) |
| --markdown | Upload images & output markdown table |
| --upload-url <url> | Custom upload endpoint (default: 0x0.st) |
Image Upload
# Default (0x0.st - no signup needed)
./scripts/upload-and-copy.sh before.png after.png --markdown
# GitHub Gist
IMAGE_ADAPTER=gist ./scripts/upload-and-copy.sh before.png after.png --markdown
Vercel Deployment Protection
If .vercel.app URL returns 401/403:
- Check Vercel CLI:
which vercel && vercel whoami - If available:
vercel inspect <url>to get bypass token - If not: Tell user to provide bypass token, take manual screenshots, or disable protection
PR Integration
# Check for gh CLI
which gh
# Get current PR
gh pr view --json number,body
# Append screenshots to PR body
gh pr edit <number> --body "<existing-body>
## Before and After
<generated-markdown>"
If no gh CLI: output markdown and tell user to paste manually.
Error Reference
| Error | Fix |
|-------|-----|
| command not found | npm install -g @vercel/before-and-after |
| could not determine executable | Use npx @vercel/before-and-after (full name) |
| 401/403 on .vercel.app | See Vercel protection section |
| Element not found | Verify selector exists on page |
TDD Red-Green-Refactor
Testing
Skill that guides Claude through the complete TDD cycle.
Web Accessibility Audit
Testing
Performs a comprehensive web accessibility audit following WCAG standards.
UAT Test Case Generator
Testing
Generates structured and comprehensive user acceptance test cases.