PR Screenshots
Capture screenshots of the Sentry UI in a web browser, lay them out in a pull request...
Install
npx skills add getsentry/skills --skill pr-screenshots -g -a claude-code -y- Repository
- getsentry/skills1.1k
- Category
- Design
- Updated
- 9d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 1,660 tokens
- Runs scripts
- No, instructions only
What it does
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`.
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.
