pr-screenshots
Skill1 starsChanged 9 days agoMITView on GitHub
Capture before and after screenshots of a visible Strata change and post them to the pull request with gh --attach, each with a caption saying what changed. Use when a branch changes the HTML report, the SVG image, or README and brand images, or when asked to add screenshots to a pull request.
- Deletes or force-pushes
- Installs packages
- Commits and pushes
16 other projects use a version of this.
Adopted by
Most recently taken up by
- torztomasz/skillstheir own version, first seen Nov 16, 2026
- NickolasBenakis/agent-playbooktheir own version, first seen Nov 15, 2026
- github/squadtheir own version, first seen Nov 8, 2026
- Venkateshvenki404224/shipcraft-skillstheir own version, first seen Nov 1, 2026
- github/awesome-copilottheir own version, first seen Oct 25, 2026
- michalklejdysz/pr-visualstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use security-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- github/awesome-copilot★ 41ksame name
- github/gh-aw★ 5.6ksame name
- lukevella/rallly★ 5.4ksame name
- github/squad★ 3.4ksame name
- levy-street/world-of-claudecraft★ 2.3ksame name
- getsentry/skills★ 1.2ksame name
- BrOrlandi/my-claude-skills★ 22same name
- nanosite-ai/nanoflow★ 15same name
- NickolasBenakis/agent-playbook★ 5same name
- bwhtech/skills★ 3same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- pr-screenshotsSkill
- strata-interpretSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Keep everything under .strata-output/ in the branch's worktree.
- Distinctive: line 56
If the view is new and has no "before", post only the "after" image and say there was nothing to compare.
- Very specific: line 76
Run gh from the branch's worktree, so it knows the repository and branch.
- Distinctive: line 87
Do not commit the images or link to a branch file to display them.
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Before and after screenshots on a Strata pull request
A reviewer should see what changed without checking out the branch. Show the same view twice, before (origin/main) and after (the branch), and say under each image what changed and where to look.
Keep everything under .strata-output/ in the branch's worktree. Git ignores it, each worktree has its own, and gh can be run from there, so no step leaves the worktree and parallel sessions do not overwrite each other's images.
1. Build both versions
From the branch's worktree, build the "before" version in a detached worktree of origin/main so the branch is not touched. The first line clears what an interrupted earlier run left behind.
git worktree remove --force .strata-output/before 2>/dev/null; rm -rf .strata-output/shots
git fetch origin main
git worktree add --detach .strata-output/before origin/main
(cd .strata-output/before && pnpm install --frozen-lockfile && pnpm build)
pnpm build
mkdir -p .strata-output/shots2. Render the same input with each
Run both builds against the same repository with the same options, so only the code differs. Strata's own repository is the default target. Do not screenshot another private repository unless the user agrees; --shareable replaces repository names, paths, and commit IDs with aliases. Never modify the target repository.
node .strata-output/before/dist/cli.js analyze . --output .strata-output/shots/before.html
node dist/cli.js analyze . --output .strata-output/shots/after.htmlFor the SVG image, use --format svg and .svg output names instead.
3. Capture at the same size and state
For a view that shows on load, use headless Chrome or Chromium with the same window size for both. If it is not found on PATH, set CHROME to the binary; on macOS it is inside the app bundle, /Applications/Google Chrome.app/Contents/MacOS/Google Chrome.
CHROME="${CHROME:-$(command -v google-chrome || command -v google-chrome-stable || command -v chromium || command -v chromium-browser)}"
if [ -z "$CHROME" ]; then echo "Set CHROME to a Chrome or Chromium binary"; else
for v in before after; do
"$CHROME" --headless=new --hide-scrollbars --window-size=1440,1000 --virtual-time-budget=5000 \
--screenshot="$PWD/.strata-output/shots/$v.png" "file://$PWD/.strata-output/shots/$v.html"
done
fiChrome may print task_policy_set or GPU errors here; they are harmless if the PNG is written.
For a state that needs interaction (a selected revision, an open panel, a hover), use browser automation, which AGENTS.md allows for visual checks. Reach the same state in both reports and use the same window size.
Crop to the changed area when the full page buries it (with any image tool, such as ImageMagick's magick in.png -crop <w>x<h>+<x>+<y> out.png, applied identically to both). Open each image and check it shows the change before posting.
If the view is new and has no "before", post only the "after" image and say there was nothing to compare.
4. Write the captions
Write the description, or the comment, to .strata-output/shots/body.md. Each image gets a caption line above it and alt text. The caption names what changed and where in the image to look; the alt text summarizes it. With several changes, use one pair per change, or list them in the caption. Reference each image by the same path you will pass to --attach:
## Screenshots
**Before.** The timeline legend (top right) lists every file; categories have no names.

**After.** The legend groups files by category, and the selected revision is outlined in the timeline.
5. Upload with gh --attach
Run gh from the branch's worktree, so it knows the repository and branch. It uploads each attached file and rewrites the matching reference in the body to the uploaded URL.
B=.strata-output/shots
gh pr create --body-file $B/body.md --attach ./$B/before.png --attach ./$B/after.png # new pull request
gh pr edit <number> --body-file $B/body.md --attach ./$B/before.png --attach ./$B/after.png # existing description
gh pr comment <number> --body-file $B/body.md --attach ./$B/before.png --attach ./$B/after.png # later round of changesFor gh pr edit, body.md must hold the whole description, not only the screenshots section. Afterwards, check with gh pr view <number> --json body that every image points at https://github.com/user-attachments/... and no ./ path is left.
Do not commit the images or link to a branch file to display them.
6. Clean up
git worktree remove --force .strata-output/before
rm -rf .strata-output/shotsDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

