screenshots-in-prs
Skill2 starsChanged 2 days agoMITView on GitHub
Use when opening or editing a pull request for a change to rendered UI.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- davidvornholt/mailboxword for word, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 1
- davidvornholt/mailbox★ 2100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ci-pipelinesSkill
- databaseSkill
- declarative-infraSkill
- frontend-designSkill
- issuesSkill
- nextjsSkill
- prsSkill
- review-fixSkill
- reviewSkill
- secrets-and-configSkill
- standards-syncSkill
- ux-uiSkill
The file
Files
Screenshots in PRs
Publish screenshots with bun standards screenshots publish <files...> from the repository root. Without config/screenshots.yaml, publishing isn't enabled: say so in the pull request and continue without screenshots. Don't fall back to another host.
Published images are public to anyone with the link and kept indefinitely, so use demo data and keep secrets and personal data out of frame.
Capture the states a reviewer needs to judge the change, at a 1280x800 viewport by default, with responsive variants when they help. When the change alters how an existing UI looks, capture a matched pair. Render Before from the base revision and After from the head, with the same viewport, route, demo data, and UI state. Leave out Before only for wholly new UI or when a still image can't show the behavior, and say why in ## Screenshots.
Give each file a descriptive kebab-case PNG name, which the command turns into the alt text. Put the Markdown it prints in a ## Screenshots section with a short caption per image, and show each pair side by side, for example in a two-column table.
Does 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.

