About pr-screenshots
pr-screenshots is a skill for adding screenshots to GitHub pull requests by uploading them to ImgBB and embedding the resulting links. It includes guidance on safe uploads, optional image expiration, and reporting upload failures.
Key features
- 01Upload screenshots to ImgBB
- 02Generate Markdown image links
- 03Set optional image expiration
- 04Check public-image privacy risks
- 05Handle upload errors
Use cases
- 01Add desktop and mobile screenshots to a PR
- 02Show seeded or test data in review images
- 03Expire uploaded images after a set period
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ petem24/ skills --skill pr-screenshotsAfter installing, type/pr-screenshotsin Claude Code to confirm it loaded.
Bundled filesupload.sh
Details
From the project READMEPR screenshots
GitHub has no API for attaching images to pull requests, so upload them to ImgBB and embed the returned links in the PR.
Before uploading
ImgBB links are public: anyone with the URL can view the image, even when the repository is private. Only upload screenshots that show seeded or test data. Never upload images showing real personal data, secrets, tokens, or credentials. If in doubt, don't upload. Describe the result in text instead.
Steps
-
Take screenshots at the sizes that matter, such as desktop and mobile. Give each file a descriptive name, because the name becomes the alt text.
-
Upload them with the
upload.shscript in this skill's directory:<skill-dir>/upload.sh output/screens/profile-desktop.png output/screens/profile-mobile.pngIt prints one markdown image link per file. Pass
-e <seconds>to have ImgBB delete the images later (for example-e 2592000for 30 days). -
Post the links to the PR, with a line on what each image shows:
gh pr comment <number> --body "$(cat <<'MD' ## Screenshots Profile page, desktop (1440px):  Profile page, mobile (390px):  MD )"If you are creating the PR yourself, put the section in the PR body instead.
If the upload fails
If the script reports that IMGBB_API_KEY is not set, stop and tell the user
this machine needs onboarding with setup.sh from their skills repository.
Don't run it yourself, look for a key, or substitute another image host.
Report other failures with the script's error message.