pr-screenshot-docs

Capture before/after UI screenshots and document visual changes for pull requests.

47|11|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill pr-screenshot-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-screenshot-docs
Source: https://github.com/majesticlabs-dev/majestic-marketplace/tree/main/plugins/majestic-engineer/skills/pr-screenshot-docs
Command: npx skills add https://github.com/majesticlabs-dev/majestic-marketplace --skill pr-screenshot-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documents UI changes for pull requests with before/after screenshots to help reviewers assess design modifications quickly.

Core Features & Use Cases

  • Before/After screenshot workflow for UI changes
  • PR description templates with visual comparison
  • Viewport guidance and best practices for consistent diffs

Quick Start

Capture before and after screenshots for a target component and attach them to the PR description.

Frequently Asked Questions about pr-screenshot-docs

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

FAQPage Schema
How do I capture before and after screenshots for UI changes in a pull request?

Before/after screenshots document UI changes by capturing the same component or page in two states—before your modification and after. This creates a visual diff that helps reviewers quickly assess design modifications without needing to check out and run the code locally.

What's the best way to show visual diffs in PR descriptions?

Include before/after screenshots in your PR description using a structured template that pairs the original state with the updated design. This creates a clear side-by-side comparison so reviewers can evaluate the visual impact of your changes immediately.

Can I automate UI screenshot capture for design reviews?

Yes. The workflow automates viewport control and element reference management to capture targeted UI components consistently. This removes manual screenshot overhead and ensures design review comparisons stay aligned across PRs.

Do I need special setup to document frontend changes in pull requests?

No special prerequisites beyond standard PR workflows. The process handles viewport guidance and best practices for consistent screenshots, making visual documentation accessible for any frontend or UI modification without extra tooling.

Why use before/after screenshots instead of just describing UI changes?

Screenshots provide objective visual evidence that reviewers can assess instantly, reducing misunderstandings about design intent. Before/after pairs show exactly what changed, making async design review faster and more accurate than text descriptions alone.

Can I host screenshots outside my repository for PR documentation?

Yes. The workflow supports optional hosting uploads, letting you store screenshots externally while linking them in PR descriptions. This keeps repositories lean while maintaining full visual documentation in your PR tooling.