Finishing a Development Branch
obra/superpowers
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Create or refresh reviewer-facing PR titles and descriptions.
Install PR Writer
$ npx skills add getsentry/skills --skill pr-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getsentry/skills pr-writer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-writer .claude/skills/pr-writer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "pr-writer" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-writer into .claude/skills/pr-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-writer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getsentry/skills/tree/main/skills/pr-writerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getsentry/skills --skill pr-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getsentry/skills pr-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/pr-writer .agents/skills/pr-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-writer" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-writer into .agents/skills/pr-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-writer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getsentry/skills --skill pr-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getsentry/skills pr-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/pr-writer .cursor/skills/pr-writer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pr-writer" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-writer into .cursor/skills/pr-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-writer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getsentry/skills.git --path skills/pr-writer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getsentry/skills --skill pr-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getsentry/skills pr-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/pr-writer .gemini/skills/pr-writer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pr-writer" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-writer into .gemini/skills/pr-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-writer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getsentry/skills pr-writerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getsentry/skills --skill pr-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/pr-writer .github/skills/pr-writer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pr-writer" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-writer into .github/skills/pr-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-writer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getsentry/skills --skill pr-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getsentry/skills pr-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getsentry/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/pr-writer .opencode/skills/pr-writer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pr-writer" agent skill from https://github.com/getsentry/skills/tree/main/skills/pr-writer into .opencode/skills/pr-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pr-writer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
pr-writer- GitHub stars
- 1k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 559 words
- Files
- 5
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create or refresh reviewer-facing PR titles and descriptions.
- Updating its title
- SKILL.md covers Inspect the Change, Core Rules, Titles and Body Shape, plus 4 more sections
- Calls gh and git
- Preparing branch changes for review
What it does
PR Writer is an agent skill from getsentry/skills, published by the product's own GitHub organization. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files (for example `EVAL.md`, `SPEC.md` and `evals/axis.config.json`).
It sits in Development. The repository describes itself as: Agent Skills used by the Sentry team for development. The licence is Apache-2.0.
When your agent uses it
- Updating its title
- Preparing branch changes for review
Example prompts
- “/pr-writer”
What it can do on your machine
Read from SKILL.md and the folder at commit d18b7aa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
PR Writer loads about 1.3k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 559 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from getsentry/skills at commit d18b7aa, republished under its Apache-2.0 licence (© getsentry). 559 words, ~1,326 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-writer/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- pr-writer
- description
- 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 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:
git branch --show-current
git status --porcelain
gh pr view --json number,title,body,url,baseRefName,headRefName
gh repo view --json defaultBranchRefIf 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:
git log "$BASE"..HEAD --oneline
git diff "$BASE"...HEADIf 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,
ci, chore, style, meta, license, and revert.
- Describe the dominant full-branch change with the narrowest accurate type and scope.
- Use
!only when the change breaks an external contract, and explain the affected surface in the body. - Avoid vague subjects such as
update,cleanup,misc,fix stuff, oraddress feedback. Do not add a trailing period. - Keep an existing title only when it still describes the whole diff.
Body Shape
Choose the minimum useful shape:
| Change | Include |
|---|---|
| Small or obvious | One concise paragraph without headings. |
| Feature, bug fix, or refactor | Changed behavior and effect; add root cause, unchanged behavior, or non-obvious approach when relevant. |
| Contract or breaking change | Affected API, schema, payload, config, permission, storage, or CLI surface; include compatibility and migration guidance. |
| Operational, visual, or workflow change | User/operator effect, measured impact, failure modes, or flow when useful. |
| Broad, generated, or cross-cutting change | Organizing principle, why the breadth is necessary, and where review should start. |
Default:
<What changed and what effect it has.>
<Why the approach, risk, migration, or review focus matters, if not obvious.>For review-feedback updates, describe the resulting PR as a whole rather than the sequence of revisions.
Show full SKILL.md (212 more words)Show less
Reviewer Aids
Use an aid only when it reduces reviewer reconstruction work:
- A compact before/after or interface example for changed contracts.
- A small Mermaid diagram for async flows or state transitions.
- A screenshot or recording note when visual evidence exists.
- A rollout, compatibility, risk, or review-order note when reviewers or adopters need it.
Introduce an artifact with one sentence explaining what reviewers should notice. Omit it when prose is clearer.
Boundaries
- Do not add default
Summary,Changes, orTest Plansections. - Omit routine validation unless it changes risk assessment or explains meaningful regression coverage. For docs, skills, copy, or config changes, omit it by default.
- Do not paste commands, CI logs, validation dumps, commit logs, placeholders, or exhaustive file lists.
- Never include customer or organization names, user emails, support ticket contents, secrets, or PII.
- Use issue references only when verified from user input, branch names,
commits, PR discussion, or tracker output.
Fixes <issue>closes;Refs <issue>only links.
Create or Update
Create new PRs as drafts. Write the body to a temporary Markdown file, then run:
gh pr create --draft --title '<title>' --body-file /tmp/pr-body.mdUpdate existing PRs with gh api:
gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER \
-f title='<title>' \
-F body=@/tmp/pr-body.mdRefresh the title and body when follow-up commits materially change scope, approach, breaking behavior, risk, migration, or review expectations. Skip typo-only, formatting-only, and rename-only follow-ups.
Examples
Small change:
The AI Customizations section now starts collapsed so it does not consume
sidebar space before users need it. Expanding it preserves the existing saved
preference behavior.Breaking contract:
Run logs now emit chunk-level records instead of one skill-level record.
Consumers that read top-level `findings` must iterate over
`chunk.findings` for each record.
Before:
```json
{"skill": "security-review", "findings": [...]}
```
After:
```json
{"schemaVersion": 1, "chunk": {"index": 1, "findings": [...]}}
```© getsentry, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in skills/pr-writer of getsentry/skills.
- SKILL.md
- EVAL.md
- SPEC.md
- evals/axis.config.json
- evals/scenarios/concise-docs-pr.json
Open the folder on GitHubat commit d18b7aa
Compare with similar skills
PR Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| PR Writer this skillgetsentry/skills | 1k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
Typescript Advanced Types
rolling-scopes/rsschool-app
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from getsentry/skills
All 27 skills in this repo- Official
Skill Scanner
getsentry/skills
Scan agent skills for security issues. An agent skill from getsentry/skills.
- Official
Gh Review Requests
getsentry/skills
Fetch unread GitHub notifications for open PRs where review is requested from a specified team or opened by a team member.
- Official
Security Review
getsentry/skills
Security code review for vulnerabilities. An agent skill from getsentry/skills.
- Official
Skill Writer
getsentry/skills
Create, synthesize, and iteratively improve agent skills following the Agent Skills specification.
- Official
Django Access Review
getsentry/skills
Django access control and IDOR security review. An agent skill from getsentry/skills.
- Official
Gha Security Review
getsentry/skills
GitHub Actions security review for workflow exploitation vulnerabilities.
Related
Categories
Questions about PR Writer
What does PR Writer do?
Create or refresh reviewer-facing PR titles and descriptions. PR Writer is an agent skill from getsentry/skills, published by the product's own GitHub organization. Create or refresh reviewer-facing PR titles and descriptions.
When should I use PR Writer?
PR Writer fits situations like: updating its title; preparing branch changes for review.
How do I install PR Writer in Claude Code?
Run `npx skills add getsentry/skills --skill pr-writer -a claude-code`. Or copy the skill folder (skills/pr-writer in getsentry/skills) into .claude/skills/pr-writer in your project. Claude Code loads it when a task matches its description.
How do I install PR Writer in Codex?
Run `npx skills add getsentry/skills --skill pr-writer -a codex`. Or copy the skill folder (skills/pr-writer in getsentry/skills) into .agents/skills/pr-writer in your project. Codex loads it when a task matches its description.
Can I use PR Writer in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getsentry/skills --skill pr-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-writer, .gemini/skills/pr-writer, .github/skills/pr-writer and .opencode/skills/pr-writer in your project.
What does PR Writer need to run?
Going by SKILL.md and its folder, PR Writer needs the command-line tools its instructions call (gh and git).
Does PR Writer access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is PR Writer safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does PR Writer use?
PR Writer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR Writer use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to PR Writer?
Skills that share tags, products or a category with PR Writer: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Writer?
getsentry (a GitHub organization, an official publisher) maintains it in getsentry/skills, which has 1,037 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 2, 2026.
Source: getsentry/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.