Skip to main content
skill CX Codex

pr-screenshots · getsentry — Claude Code skill: features and installation

The pr-screenshots Claude Code skill captures Sentry UI screenshots for pull request descriptions. It activates when a PR changes frontend elements users can see.

Apache-2.0 232 installs ★ 1,193 updated 2026-10-23

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add getsentry/skills --skill pr-screenshots -a claude-code
Open on GitHub

What pr-screenshots does

The skill captures changed Sentry screens and lays the images out in a pull request description. For visual edits, it compares the old and new interface, then separates unchanged locations into their own table. It also accounts for different UI states and themes.

Screenshots come from the running app on the PR branch and the base branch; CSS injection and DOM edits are forbidden. Before upload, images are checked for secrets and private values are obscured. Uploading with --attach requires gh 2.99.0 or newer. If gh rejects the flag, it must be upgraded.

What it helps with

  • show a frontend change with before-and-after screenshots
  • separate changed screens from unchanged locations
  • capture loading, error, and empty states
  • inspect screenshots for secrets before uploading

Example prompts for the agent

  • Capture before-and-after screenshots of the Sentry UI changes in this pull request.
  • Add tables of changed and unchanged locations to the PR description.
  • Refresh screenshots for affected screens after a new commit.

How to install pr-screenshots

1Skills CLI (Vercel)

npx skills add getsentry/skills --skill pr-screenshots -a claude-code

2Manually: put the files in place

~/.claude/skills/pr-screenshots/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pr-screenshots/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about pr-screenshots

How do I install pr-screenshots in Claude Code?

Run npx skills add getsentry/skills --skill pr-screenshots -a claude-code. The skill file is installed at ~/.claude/skills/pr-screenshots/SKILL.md.

What does pr-screenshots do?

It captures real app screens before and after frontend changes, checks images, and adds them to the pull request description in tables.

What does pr-screenshots need to work?

The app must run on both the PR branch and the base branch. Uploading screenshots with --attach requires gh 2.99.0 or newer.

Source text

SKILL.md · Apache-2.0
---
name: pr-screenshots
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`.
when_to_use: When a pull request intentionally modifies the frontend such that users would see a difference.
---

# 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

| Rule | Detail |
|------|--------|
| Real build only | Screenshot the running app on the PR branch for "after" and on the base branch for "before". Never screenshot a story, mock page, or harness built for the PR, unless the change is to that story. |
| No injected changes | Never inject CSS or change the DOM to imitate the change. Stubbing API responses is fine; the frontend code must be the real code. |
| Seed missing data | If a state needs data no account has, create it in a local environment. Do not report a location as impossible to screenshot until seeding has been tried, and then say exactly what failed. |
| Identical framing | Capture the same region at the same dimensions for both shots of a pair, even when one state is taller. Emulate a fixed viewport instead of resizing the user's own browser window. |
| Context | Keep the heading or label that names the thing, nearby rows or controls, and a little padding on every side. For a hover, focus, or open-menu state, keep the trigger and the overlay in one frame. When the bug only makes sense in its page, show more of the page. |
| No empty bands | Crop out browser chrome, app navigation, and regions the change does not touch. For full-width layouts, shrink the viewport instead of leaving wide blank space beside short content. |

## Step 3: Redact and Audit

1. Blur only private values: emails, usernames, customer or organization names
   and slugs, IDs, and internal hostnames. Keep keys, labels, and non-sensitive
   values readable, such as `browser.name` → `chrome`.
2. Paint over each region before blurring it so the blur can't be reversed.
   Never use solid black or dark boxes, and never blur whole tables or rows.
3. Read every image before uploading it and check for credentials: tokens, auth
   headers, cookies, signed URLs, secret keys, and webhook endpoints. Remove
   real leaks. Do not treat a public client DSN as a leak.

## Step 4: Choose the Table Shape

| Change | Shape |
|--------|-------|
| Visual change to existing UI | **Changed** table, plus an **Unchanged** table for locations the diff reaches that render the same. |
| New page or feature | No before/after. A few "after" screenshots, each introduced by a short sentence. When the new UI appears in several locations, use a `Location \| Screenshot` table instead. |
| Alternatives with no "before", such as prototype treatments or design options | `Treatment \| Screenshot` table, one row per alternative. |
| A change that differs by theme | Add a light and a dark row for each location, such as `Explore › Logs, dark`. For new UI, use `Light \| Dark` columns instead. |

Pixel-diff every before/after pair. Move a pair with no
visible difference, including anti-aliasing noise, to **Unchanged** with one
image. Leave out a table that would be empty.

```markdown
**Changed**

| Location | Before | After |
| --- | --- | --- |
| Explore › Logs | ![Explore › Logs before](./shots/logs-before.png) | ![Explore › Logs after](./shots/logs-after.png) |
| Explore › Logs, loading | ![Explore › Logs, loading before](./shots/logs-loading-before.png) | ![Explore › Logs, loading after](./shots/logs-loading-after.png) |

**Unchanged**

| Location | Before & After |
| --- | --- |
| Trace view › Logs | ![Trace view › Logs](./shots/trace-logs.png) |
```

Formatting rules:

- Name the first column `Location`, or `Treatment` for alternatives. Never
  leave its header empty.
- Write each location as a `›` breadcrumb of what the reader clicks through,
  then a comma and the state: `Monitors › cron monitor details › Check-Ins, loading`.
- Use only the columns shown above. Never add a "What changed" or notes column;
  the screenshots show the change.
- Give each image alt text naming its row and side, such as
  `Explore › Logs before`.
- Label the tables with bold `**Changed**` and `**Unchanged**` lines. Do not add
  an intro sentence describing where or how the screenshots were taken.
- Use Markdown tables by default, because `gh --attach` rewrites only Markdown
  image references. Switch to an HTML table only when cells must span rows, such
  as a light and dark row under one location
  (`Location | Theme | Before | After` with `rowspan="2"` on the location cell).
  Do not add `align` attributes.

## Step 5: Upload With gh

`gh pr create`, `gh pr edit`, `gh pr comment`, and the matching `gh issue`
commands accept `--attach '<path>#<alt text>'` (gh 2.99.0+). If `gh` rejects
the flag, ask the user to upgrade it. Do not push asset branches, commit
images, or upload through the browser's comment box.

Write the body file with relative Markdown image references, then pass the same
paths to `--attach`. gh uploads each file and rewrites the matching reference
to the uploaded URL in place:

```bash
gh pr edit 123 --body-file pr-body.md \
  --attach './shots/logs-before.png' --attach './shots/logs-after.png'
```

| Behavior | Detail |
|----------|--------|
| Paths | Resolve against the current directory, and must match the body's references exactly. |
| Unreferenced attachments | Get appended to the end of the body as `![alt](url)`. |
| No body flag | `gh pr edit --attach` keeps the existing body and appends the images. |
| HTML tables | `<img src="./x.png">` is not rewritten. Attach first, copy the appended URLs into the `<img>` tags, delete the appended lines, then write the final body with `--body-file`. |

Before writing a body the user may have edited, fetch it again and compare it
with the version you last read. Keep the user's wording and table edits, swap in
only your rows and URLs, and keep the body's line endings. Removing an image
from the body does not delete the uploaded file.

## Step 6: Keep Screenshots Current

When a later commit changes what a screenshot shows, retake the affected pairs,
re-check which pairs belong in **Changed** and **Unchanged**, and update the
body without waiting to be asked.

© getsentry · Apache-2.0 · getsentry/skills

Similar skills

All skills for Frontend and UI →

pr-screenshots by other authors comes first.

pr-screenshots official github pr-screenshots — a GitHub Copilot skill that puts before/after screenshots straight into pull request descriptions. Kicks in on PRs where something visible changed: layout, charts, forms, error text. CX Codex +1 141installs sentry-pr-code-review getsentry sentry-pr-code-review extracts Seer Bug Prediction comments from GitHub pull requests, verifies potential bugs in the code, and applies fixes directly. CX Codex +1 642installs sentry-setup-releases getsentry sentry-setup-releases wires Sentry release tracking and deploy monitoring to connect errors with commit culprits. Useful when issues show an unknown release or lack suspect commits. CX Codex +1 1,700installs workflow-progress-screenshots MengTo workflow-progress-screenshots instructs coding agents to capture and send real visual progress screenshots automatically. Built for UI, 3D, charts, and motion tasks. CX Codex +1 682installs ui-screenshots official github ui-screenshots — a skill that photographs web pages and desktop windows so the agent can document visual changes before and after a code edit. CX Codex +1 209installs before-and-after vercel-labs before-and-after turns existing screenshots and screen recordings into a before/after or preview block inside a GitHub pull request description. CX Codex +1 3,200installs deslop davila7 deslop cleans AI-generated clutter from a branch before merging code. It inspects diffs against main to strip needless comments, type workarounds, and unneeded guards. CX Codex +1 437installs

From the same set27

The whole set →
sred-project-organizer sred-project-organizer organizes annual engineering projects into SRED-compliant documentation and creates structured Notion pages. CX Codex +1 2,200installs sred-work-summary Collects GitHub PRs, Notion pages, and Linear issues from a work period, then groups their links into projects in a private Notion document. Useful for preparing an SRED work summary. CX Codex +1 2,200installs typing-exclusion-worker typing-exclusion-worker removes Python modules from mypy exclusion lists in pyproject.toml, fixes typing errors, and runs scoped validation. Built for parallel typing debt workers. CX Codex +1 1,700installs pr-link-issue pr-link-issue adds a GitHub issue and its linked Linear ticket to the current PR description. Use it when a pull request needs references to the work it addresses. CX Codex +1 1,400installs triage-frontend-issues triage-frontend-issues — a skill that clears noise from the sentry/javascript issue queue in Sentry and leaves real bugs for a human. CX Codex +1 1,400installs document-api-endpoint document-api-endpoint is a Claude Code skill that documents and types Sentry API endpoints with drf-spectacular, resolving drift between OpenAPI schemas and live responses. CX Codex +1 1,300installs secret-serialization secret-serialization catches credentials leaking into logs, traces, and error reports via generated serialization like dataclass repr, model_dump, or JSON.stringify. CX Codex +1 494installs security-model This skill helps define, review, and update SECURITY_MODEL.md files for security audit tools. Use it to configure threat models, trust boundaries, and invariants in your repository. CX Codex +1 236installs

Project sponsors

Companies that keep this analytics open