PR Writer
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.
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-writergit clone --depth 1 https://github.com/getsentry/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/pr-writer ~/.claude/skills/pr-writerPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# PR Writer Write the PR body as a cover note for reviewers, not a changelog, template, validation log, or file-by-file summary. ## Inspect the Change Requires authenticated `gh`. Inspect the current branch, working tree, PR, base branch, commits, and full diff: ```bash git branch --show-current git status --porcelain gh pr view --json number,title,body,url,baseRefName,headRefName gh repo view --json defaultBranchRef ``` If `gh pr view` reports that no PR exists, continue with first-time PR creation. For an existing PR, use its `baseRefName`; otherwise use the repository default branch. Set `BASE`, then inspect: ```bash git log "$BASE"..HEAD --oneline git diff "$BASE"...HEAD ``` If on `main` or `master`, create a feature branch first. Ensure intended changes are committed and review the whole branch diff, not only the latest commit or existing PR text. ## Core Rules - Describe concrete changed behavior, affected surfaces, and reviewer impact before implementation detail. - Explain motivation, risk, tradeoffs, migration, or review focus only when useful. - Use the smallest structure that makes the change easier to review. - Replace internal prompt or process terminology with specific behavior. - When refreshing a PR, rewrite around the current full diff without narrating review history. ## Titles Use `<type>(<scope>): <subject>` or `<type>: <subject>`. Allowed types: `feat`, `fix`, `ref`, `perf`, `docs`, `test`, `build`,
Details
- Skill name
pr-writer- Repository
- getsentry/skills
- Path
skills/pr-writer/SKILL.md- License
- Apache-2.0
- Repo updated
- 14 November 2026
- Listed in
- heilcheng/awesome-agent-skills
FAQ
What does the PR Writer skill do?
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.
How do I install the PR Writer 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 Writer 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.
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
PR Screenshots
1.2kgetsentry/skills
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`.
Dd File Issue
1kDataDog/pup
File GitHub issues to the right repository (pup CLI or plugin)
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.