domains / families / software-engineering / pr-writer

pr-writer

combined

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. Create pull requests following Sentry's engineering practices.

When to use

• You are ready to open a pull request and need a structured description based on the committed branch diff.
• You want the PR body to capture what changed, why it changed, and any reviewer context.
• You are using GitHub CLI and need a repeatable PR-writing workflow rather than writing the description ad hoc.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

Both copies describe the same task (writing a reviewer-facing PR title and body via gh), but they disagree on the required body structure and on how to create/update the PR. The getsentry copy forbids default Summary/Changes/Test Plan sections, prescribes a minimum-shape body, and uses a temporary body file for both create and update. The sickn33 copy mandates a four-paragraph structure (what, why, alternatives, context), uses a heredoc for creation, and explicitly warns that gh pr edit is broken. Crowning one copy would hide a real alternative workflow and conflicting constraints.