pr-writer

# PR Writer Create pull requests following Sentry's engineering practices. **Requires**: GitHub CLI (`gh`) authenticated and available. ## 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. ## Prerequisites Before creating a PR, ensure all changes are committed. If there are uncommitted changes, run the `sentry-skills:commit` skill first to commit them properly. ```bash # Check for uncommitted changes git status --porcelain ``` If the output shows any uncommitted changes (modified, added, or untracked files that should be included), invoke the `sentry-skills:commit` skill before proceeding. ## Process ### Step 1: Verify Branch State ```bash # Detect the default branch — note the output for use in subsequent commands gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name' ``` ```bash # Check current branch and status (substitute the detected branch name above for BASE) git status git log BASE..HEAD --oneline ``` Ensure: - All changes are committed - Branch is up to date with remote - Changes are rebased on the base branch if needed ### Step 2: Analyze Changes Review what will be included in the PR: ```bash # See all commits that will be in the PR (substitute detected branch name for...