pr-screenshots

Capture Playwright screenshots and embed them into GitHub pull request descriptions.

9|1|Updated Jul 21, 2025
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill pr-screenshots
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-screenshots
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/pr-screenshots
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill pr-screenshots

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewers often need to see rendered pages or UI changes without checking out branches or running local dev servers, and screenshots are frequently excluded or committed incorrectly which bloats repositories and stalls reviews.

Core Features & Use Cases

  • Capture with Playwright: Reuse existing Playwright tests or run a minimal capture script to produce deterministic screenshots of pages and components.
  • Host on a temporary branch: Publish only the screenshot files to an orphan branch so raw GitHub URLs can render images in PR bodies without committing artifacts to feature branches.
  • Embed into PR descriptions: Use raw.githubusercontent.com links and gh pr edit (or the web UI) to include inline images in the PR description so reviewers see visuals immediately.
  • Cleanup & hygiene: Delete the temporary branch after merge and gitignore local screenshot folders to prevent repository bloat.

Quick Start

Run your Playwright capture to save screenshots, push them to a temporary orphan branch called screenshots-temp, and update the PR body with raw.githubusercontent.com URLs to embed the images for reviewers.

Frequently Asked Questions about pr-screenshots

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

FAQPage Schema
How do I embed Playwright screenshots into a GitHub pull request description?

To embed Playwright screenshots into a GitHub pull request description, push the captured images to a temporary orphan branch and insert raw.githubusercontent.com links into the PR body using gh pr edit. This provides inline visual diffs for reviewers without bloating the repository.

What is the best way to show UI changes in a pull request without committing image files?

The best way to show UI changes without committing image files is hosting screenshots on a temporary orphan branch. You can then use raw.githubusercontent.com URLs to render the images directly in the PR description, keeping your feature branches clean and avoiding repository bloat.

Can I use gh CLI to update a PR body with visual review screenshots?

Yes, you can use the GitHub CLI to update a PR body with visual review screenshots. By running the gh pr edit command, you can append or modify the pull request description to include raw GitHub image links hosted on a temporary orphan branch.

Does embedding PR screenshots require Playwright or equivalent screenshot tooling?

Embedding PR screenshots requires Playwright or equivalent screenshot tooling to capture the rendered pages. You can reuse existing Playwright tests or run a minimal capture script to generate the deterministic screenshots needed for the visual review.

How do I clean up temporary screenshot branches after a PR is merged?

To clean up temporary screenshot branches after a PR is merged, delete the temporary orphan branch used for hosting the images. You should also gitignore local screenshot folders to prevent accidentally committing artifacts and stalling future reviews.