← Explore all skills

DEVELOPMENT WORKFLOW / getsentry

Reviewer-Facing PR Writing

Write or refresh PR titles and bodies from the full branch change and its reviewer impact.

“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.”

01 / THE REASONING

Why this made the selection.

  • New pull requests are created as drafts after the whole branch diff is read, not from the latest commit alone.
  • The body is a reviewer note. Default Summary, Changes, and Test Plan headings are forbidden.
  • The definition selects the existing PR base or repository default and separates issue-linking from issue-closing language.
  • Replace stale PR framing after scope changes

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • skills/pr-writer/SKILL.md
  • LICENSE
  • README.md

Our findings

  • It needs a logged-in gh and writes a draft with gh pr create, or patches an existing pull request. It does not merge.
  • Customer names, emails, ticket contents, secrets, and other personal data are banned from the text.
  • It does not paste CI logs or a file list, and it does not invent an issue reference that was not already in the branch or the tracker.
  • The definition selects the existing PR base or repository default and separates issue-linking from issue-closing language.
  • The body-shape table asks broad or generated changes to explain why their breadth is necessary and where review should begin; reviewer aids are included only when they reduce reconstruction work.

Not established by this review

  • The resource was not executed and its tools were not called.
  • No pull request was created or edited.
  • No skill execution, authenticated service operation, or outcome benchmark was performed.
  • Not executed: it was not installed or run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Add a skill to your workflow.

Upstream setup instructions ↗

DOCUMENTED COMMAND

npx skills add getsentry/skills/skills/pr-writer

Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.

Optional: install the reviewed revision

Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.

npx skills add https://github.com/getsentry/skills/tree/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/pr-writer
  1. Install the pinned skill directory interactively, retaining its bundled references and scripts.
  2. Inspect branch status, current PR/base and the complete branch diff; verify any linked issue before using a closing reference.
  3. Write the body to a file, then create a draft or update the existing PR only within authorized publication scope.

Before you start

  • git and authenticated gh
  • A reviewable committed branch

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Pinned skill definition ↗Checked

    https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/pr-writer/SKILL.md

    Supports: summary, whySelected, bestFor, limitations, install, access, review

  2. https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/README.md

    Supports: install

  3. Apache-2.0 licence ↗Checked

    https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/LICENSE

    Supports: license

  4. https://raw.githubusercontent.com/getsentry/skills/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/pr-writer/SKILL.md

    Supports: review.findings, bestFor

Evidence & Ask