skills.rest
acmeleme
acmelemeOFFICIAL
Explore all skills by this author →
GitHub

pr-screenshots

Automates embedding screenshots from playscript into pull-request descriptions.

Updated Nov 11, 2025
Search Tags:#automation#screenshots#github#playwright#pr#pr-description#visual-review
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill pr-screenshots-acmeleme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-screenshots
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.squad/templates/skills/pr-screenshots
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill pr-screenshots-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright.

What problem does it solve?

Reviewers often struggle to assess visual changes in PRs without running the app locally. This skill captures Playwright screenshots and embeds them in the PR description to provide immediate visual context for faster validation.

Core Features & Use Cases

  • Capture screenshots from Playwright tests when UI changes occur in a PR.
  • Host screenshots to generate stable image URLs and embed them with markdown in PR descriptions.
  • Improve review speed and accuracy by presenting visual evidence alongside code changes.

Quick Start

Run the capture-pr-screenshots script and paste the resulting image links into the PR description.

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 PR description?▼

To embed Playwright screenshots in a GitHub PR description, you need a script that captures images during tests, hosts them at stable URLs, and inserts image markdown directly into the PR description body.

What is the best way to provide visual context for UI changes in a pull request?▼

Providing visual context for UI changes in a pull request is best achieved by capturing Playwright screenshots and embedding them directly in the PR description, allowing reviewers to validate visual states immediately without running the app locally.

Do I need Playwright already set up to automate PR screenshots?▼

Yes, you need Playwright already set up to automate PR screenshots, as the process requires a Playwright configuration to capture screenshots of UI states before hosting and embedding them in the PR description.

How do I host Playwright screenshots to get stable URLs for PR descriptions?▼

To host Playwright screenshots for stable URLs in PR descriptions, you must run a process that stores the captured image files and generates persistent links, which are then formatted as image markdown and inserted into the PR description.

When should I add screenshots to a PR description for visual review?▼

You should add screenshots to a PR description for visual review when PRs introduce UI changes or docs updates and reviewers need immediate visual context to quickly validate different UI states alongside the code changes.

Related Skills

Explore More Software Engineering Skills→
jonnymuirjonnymuir
1

docs-walkthrough-screenshots

Automates UI screenshot generation for Umbraco.Prism Aspire stack documentation using Playwright and workflows.

Community
Advanced
SuperCorksSuperCorks

address-pr-comments

Fetch GitHub PR reviews via gh CLI and apply latest reviewer feedback.

Community
Advanced
samjhechtsamjhecht
4

frontend-visual-regression-testing

Compare UI component screenshots against baselines to detect visual regressions.

Community
Advanced
dwmkerrdwmkerr
101

ark-dashboard-testing

Automate Ark Dashboard UI testing with Playwright and generate PR-ready screenshots.

Community
Advanced