PR Screenshots
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`.
Install
/plugin marketplace add getsentry/skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add getsentry/skills --skill pr-screenshotsgit clone --depth 1 https://github.com/getsentry/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/pr-screenshots ~/.claude/skills/pr-screenshotsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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. |
Details
- Skill name
pr-screenshots- Repository
- getsentry/skills
- Path
skills/pr-screenshots/SKILL.md- License
- Apache-2.0
- Repo updated
- 14 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the PR Screenshots skill do?
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`.
How do I install the PR Screenshots skill?
Claude Code plugin: /plugin marketplace add getsentry/skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is PR Screenshots popular?
It lives in getsentry/skills, which has 1,179 GitHub stars and 70 forks, and is included in 1 curated skill list.
Related skills
Doc Coauthoring
1.2kgetsentry/skills
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Brand Guidelines
1.2kgetsentry/skills
Write copy following Sentry brand guidelines. Use when writing UI text, error messages, empty states, onboarding flows, 404 pages, documentation, marketing copy, or any user-facing content. Covers both Plain Speech (default) and Sentry Voice tones.
Code Simplifier
1.2kgetsentry/skills
Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
PR Writer
1.2kgetsentry/skills
Create or refresh reviewer-facing PR titles and descriptions. Use when opening a PR, updating its title or body, or preparing branch changes for review.
PR Link Issue
1.2kgetsentry/skills
Append a GitHub issue link and its Linear ticket to the current PR's description. Use when asked to "link issue to pr", "fill in issue and linear in pr", "add issue refs to pr", or when given a GitHub issue URL and asked to attach it to the current PR. Resolves the Linear ticket automatically from the issue's linear-linkback comment.
Sw Chinese Opera Qupai
2.1kjtydhr88/screenwriting-skills
Chinese opera playwriting for the qupai (曲牌体) system — 元杂剧, 明清传奇, 昆曲, 川剧高腔, where sung text is filled into fixed tune patterns (填词) rather than built from paired lines varied by metre. Covers stage vs study (李渔 vs 吴梅/王季烈), the 清曲/剧曲 switch, the zaju branch (四折一楔子, one 宫调 and one rhyme per act, 一人主唱, 题目正名), the chuanqi branch (出, 副末开场, 南北合套, 集唐下场诗), tune-filling (格律, 前腔/换头/幺, 衬字, 务头, 尾声, 四十禁), the seventeen 宫调 and their affects, 套数, 排场 alternation, the spoken-to-sung cue, 帮腔, adaptation, and modern practice. From 李渔《闲情偶寄》, 吴梅《顾曲麈谈》《曲学通论》, 王季烈《螾庐曲谈》, 孔尚任's 凡例, 关汉卿, 汤显祖, 魏明伦. Use when writing or
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.