Capture, host, and embed screenshots in GitHub PR descriptions.
npx skills add https://github.com/barichter/squad --skill pr-screenshots-barichter
Please help me install this Agent Skill. Skill: pr-screenshots Source: https://github.com/barichter/squad/tree/main/.squad/skills/pr-screenshots Command: npx skills add https://github.com/barichter/squad --skill pr-screenshots-barichter
This skill solves the issue of reviewers needing to see visual changes in pull requests without checking out the branch, by automatically embedding screenshots in PR descriptions.
Use the pr-screenshots skill to create screenshots for your pull request and embed them automatically in the PR description.
High-intent search queries and answers about installing and using this skill.
To embed screenshots in a GitHub pull request description, you can automate the process by capturing images with Playwright, hosting them on a temporary branch to generate URLs, and inserting those links into the PR markdown. This allows reviewers to see visual changes without checking out the branch.
Yes, you can use Playwright for automated PR image embedding. The skill captures screenshots using Playwright, uploads them to a temporary GitHub branch to generate accessible URLs, and embeds those image links directly into the pull request description markdown for visual review.
Yes, you need the GitHub CLI installed to automate PR screenshot hosting. The skill relies on the GitHub CLI to manage temporary branches, upload captured screenshot assets, and generate raw URLs for embedding the images into the pull request description.
The best way to show UI changes in a pull request without branch checkout is to embed screenshots directly in the PR description. This approach captures visual artifacts, hosts them on a temporary branch, and inserts the image URLs into the markdown for immediate reviewer access.
Temporary branch cleanup after a PR is merged involves automatically deleting the branch used to host the embedded screenshots. Once the pull request is merged, the temporary branch is removed to prevent repository clutter while keeping the image links active in the PR history.
A limitation of hosting PR screenshots on a temporary branch is that the branch must be managed carefully to avoid clutter, requiring cleanup after the pull request is merged. Additionally, this workflow depends on both Playwright and the GitHub CLI being properly configured in the environment.
berkcangumusisikGenerate GitHub pull requests from the current branch with gh.
usepowershellCapture Playwright screenshots and embed them into GitHub pull request descriptions.
murphytruemanGenerate CI/CD pipeline configurations for design system quality checks.
CaptainCrouton89Manage Cloudflare R2 buckets and objects with the Wrangler CLI.
