screenshots-in-prs · git:20260902.d6f0931 · 2026-09-02 · sha256 02638bbe11fbbb4f
screenshots-in-prs git:20260902.d6f0931A
Immutable. This exact content never changes and is served at /api/v1/blob/02638bbe11fbbb4f.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2lqc33wckj43f6rk/02638bbe11fbbb4f8e0cf9f51c965fe89ea7e8c4ce5b6e907bcf56dd524a1cf5.json
Then /plugin install screenshots-in-prs@markdownregistry-2lqc33wckj43f6rk in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: screenshots-in-prs description: Must be used when opening or updating a pull request that changes rendered UI. Covers capturing screenshots, publishing them, and embedding them in the PR description. --- # Screenshots in PRs - If `config/screenshots.yaml` is absent, state in the PR that screenshot publishing is not enabled and continue without screenshots. Do not use another host. - Capture the states needed to review the change. Include responsive variants when they clarify it. - For every change to an existing UI's visible presentation, capture matched `Before` and `After` screenshots. Render `Before` from the PR's base revision and `After` from its head with the same viewport, route, demo data, and UI state, then present the pair side by side. Omit `Before` only for wholly new UI or when a still image cannot show the changed behavior, and state why in `## Screenshots`. - Default to a 1280x800 viewport. Use descriptive kebab-case PNG filenames; the filename becomes the alt text. - Published URLs are public and permanent. Use demo data and exclude secrets and personal data. - From the repository root, run `bun standards screenshots publish <files...>`. - Put the printed Markdown in a `## Screenshots` section with short captions. Use a two-column table when comparing images side by side helps the review.