before-and-after

Capture before-and-after screenshots from URLs or image paths to highlight visual differences.

2|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/raiden076/Prism --skill before-and-after-raiden076
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: before-and-after
Source: https://github.com/raiden076/Prism/tree/main/.agents/skills/before-and-after
Command: npx skills add https://github.com/raiden076/Prism --skill before-and-after-raiden076

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser, gh, curl, pbcopy, xclip, and includes scripts (resource) components.

What problem does it solve?

Manual UI diffing is tedious and error-prone; this skill automates capturing before/after visuals for web pages or elements to document changes and facilitate reviews.

Core Features & Use Cases

  • Automated visual captures: take before and after screenshots from two URLs or two local image paths, with optional CSS selectors to target specific elements.
  • Diff-ready output: supports uploading images via adapters to share or attach to PRs, and can generate markdown-ready summaries.
  • Use Case: verify UI changes after a deploy by comparing production vs preview versions and filing a diff in your PR.

Quick Start

Provide two URLs or two image paths and run the capture to generate before/after visuals.

Frequently Asked Questions about before-and-after

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

FAQPage Schema
How do I automate visual regression testing for UI changes across different URLs?

Automate visual regression testing by capturing before and after screenshots from two URLs to compare web pages and highlight visual differences. This skill supports optional CSS selectors and viewport controls for deterministic UI change verification across multiple environments.

Can I compare specific page elements instead of full page screenshots?

Yes, you can compare specific page elements by providing optional CSS selectors to target specific elements during the before and after screenshot capture. This allows precise visual diffing of individual UI components rather than capturing the entire web page.

How do I generate PR-ready visual diffs for UI verification?

Generate PR-ready visual diffs by capturing before and after screenshots of your web pages and running the included scripts to upload images and produce markdown-ready summaries. This automates documenting UI changes and facilitates design QA reviews directly in your pull requests.

Does this visual diff tool require a browser automation dependency?

Yes, this visual diff tool requires the agent-browser dependency for automated screenshot capture, along with gh, curl, pbcopy, and xclip for uploading images and generating markdown summaries. These dependencies enable deterministic capture and PR-ready output generation.

What is the best way to verify UI changes after a deploy?

The best way to verify UI changes after a deploy is to compare production versus preview versions by capturing before and after screenshots from both URLs. This skill automates the visual comparison and can file the resulting diff directly into your PR for review.

Can I use local image paths for before and after comparison?

Yes, you can use local image paths as an alternative to URLs for before and after comparison. The skill accepts two image paths as input to generate visual diffs, providing flexibility when web pages are not accessible or when comparing previously captured screenshots.