PR Screenshot Comparison
Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
Install
npx skills add petekp/claude-code-setup --skill pr-screenshot-comparisongit clone --depth 1 https://github.com/petekp/claude-code-setup.git /tmp/claude-code-setup
mkdir -p ~/.claude/skills
cp -r /tmp/claude-code-setup/skills/pr-screenshot-comparison ~/.claude/skills/pr-screenshot-comparisonPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# PR Screenshot Comparison Create a single, reviewer-friendly image that makes a visual UI change easy to evaluate. ## Product evidence rule A PR screenshot is evidence of the product, not a design illustration. Every panel must come from the actual product route running the exact base or PR commit. It must use the real app shell, routing, authentication boundary, and data path. A component harness, Storybook story, static reconstruction, fabricated destination page, or mock data screen does not qualify as product evidence. Do not attach one to a PR or describe it as an application screenshot. If authentication or data blocks the route: 1. Start or reuse the project's canonical local environment. 2. Reuse an authenticated browser session when one is available. If sign-in needs the user, request the smallest necessary handoff. 3. If the actual route still cannot be reached, stop and report the blocker. A missing screenshot is more accurate than fabricated proof. Build a harness only when the user explicitly asks for component-level evidence. Label it **Component harness** in the image and PR copy. Never mix it with or substitute it for product screenshots. ## Internal data policy For a verified private or internal PR, use the actual product data on screen, including PHI. Do not replace names, records, or content with fake data solely for privacy. These screenshots are internal review artifacts.
Details
- Skill name
pr-screenshot-comparison- Repository
- petekp/claude-code-setup
- Path
skills/pr-screenshot-comparison/SKILL.md- License
- MIT
- Repo updated
- 26 October 2026
FAQ
What does the PR Screenshot Comparison skill do?
Create clear, polished before-and-after screenshots from the actual running product for a GitHub pull request. Use when a UI change needs visual proof: capture matching product states, crop to the relevant UI, stitch and caption one comparison image, attach it natively to the PR, and keep the image out of the repository.
How do I install the PR Screenshot Comparison skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add petekp/claude-code-setup --skill pr-screenshot-comparison. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is PR Screenshot Comparison popular?
It lives in petekp/claude-code-setup, which has 49 GitHub stars and 10 forks.
Related skills
Catch Up
49petekp/claude-code-setup
Give the human a fast, plain-English catch-up on what changed in the project: what the agents did, why, and what decisions need their input. Use when the user asks to "catch me up", "what changed", "where are we", "recap", "brief me", "give me the rundown", "what did you do", "summarize the session", or "fill me in", or otherwise wants to get back up to speed after being away.
Clean Copy
49petekp/claude-code-setup
Cut interface copy that should not exist. Captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up or tighten copy.
Code Comments
49petekp/claude-code-setup
Write, review, or remove code comments. Use when adding comments or doc comments, reviewing the comments in a diff, or cleaning up or removing comments.
PR Self Review
49petekp/claude-code-setup
Draft explanatory author-context comments for the user's own PR or local diff. Use for self-review or reviewer context, not a formal review submission. Posting requires approval.
PR Description
49petekp/claude-code-setup
Write or update a GitHub PR description a teammate understands in one quick read: clear before/after behavior, useful visual evidence, and plain sentences grounded in the diff and real verification. Use when opening a PR or editing its description.
Finishing a Development Branch
49sodiumjoe/dotfiles
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.