# PR Screenshots

Capture screenshots of the Sentry UI in a web browser, lay them out in a pull request...

- Repository: https://github.com/getsentry/skills (1107 stars)
- Category: Design
- License: Apache-2.0
- Last updated: 2026-10-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add getsentry/skills --skill pr-screenshots -g -a claude-code -y`
Codex: `npx skills add getsentry/skills --skill pr-screenshots -g -a codex -y`
Cursor: `npx skills add getsentry/skills --skill pr-screenshots -g -a cursor -y`
Gemini CLI: `npx skills add getsentry/skills --skill pr-screenshots -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add getsentry/skills`

## Description

Capture screenshots of the Sentry UI in a web browser, lay them out in a pull request description as before/after tables, and upload them with `gh --attach`.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# PR Screenshots

Screenshots in a PR are QA evidence. Each one shows what the real product
renders at one location, framed so a reviewer who has never opened the page can
tell what changed.

## Step 1: List the Locations

List every place in the product that the diff reaches: each page, drawer,
modal, or widget that renders a changed component, found by tracing its
callers and consumers. Then add the states the change affects at each of them,
such as loading, error, empty, hover, selected, menu open, expanded, scrolled,
narrow viewport, and light or dark theme.

Never group surfaces into one row: for example,
"GridEditable, as in Discover, dashboards and insights" is three rows.

## Step 2: Capture From the Real Product

The rest: https://github.com/getsentry/skills/blob/HEAD/skills/pr-screenshots/SKILL.md