sickn33/antigravity-awesome-skills/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 intended changes are committed and reviewed. Preserve unrelated dirty/staged work; a PR request does not authorize automatically committing every file. Use an installed commit workflow only for the authorized diff.

# Check for uncommitted changes
git status --porcelain

If intended files are uncommitted, prepare only those files using the repository workflow; an absent commit skill is not a blocker to ordinary authorized Git work. If the client requires qualified skill names, use the qualifier for the plugin that supplied this skill.

Process

Step 1: Verify Branch State

# Detect the default branch — note the output for use in subsequent commands
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'

# 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:

# See all commits that will be in the PR (substitute detected branch name for BASE)
git log BASE..HEAD
 
# See the full diff
git diff BASE...HEAD

Understand the scope and purpose of all changes before writing the description.

Step 3: Write the PR Description

Use the repository PR template and required checklist first. Where no local template applies, use this Sentry-style structure:

<brief description of what the PR does>
 
<why these changes are being made - the motivation>
 
<alternative approaches considered, if any>
 
<any additional context reviewers need>

Avoid unless repository policy requires them:

• Repetitive "Test plan" sections
• Checkbox lists duplicating recorded testing evidence
• Redundant summaries of the diff

Do include:

• Clear explanation of what and why
• Links to relevant issues or tickets
• Context that isn't obvious from the code
• Notes on specific areas that need careful review

Step 4: Create the PR

gh pr create --draft --title "<type>(<scope>): <description>" --body "$(cat <<'EOF'
<description body here>
EOF
)"

Title format follows commit conventions:

• feat(scope): Add new feature
• fix(scope): Fix the bug
• ref: Refactor something

PR Description Examples

Feature PR

Add Slack thread replies for alert notifications
 
When an alert is updated or resolved, we now post a reply to the original
Slack thread instead of creating a new message. This keeps related
notifications grouped and reduces channel noise.
 
Previously considered posting edits to the original message, but threading
better preserves the timeline of events and works when the original message
is older than Slack's edit window.
 
Refs SENTRY-1234

Bug Fix PR

Handle null response in user API endpoint
 
The user endpoint could return null for soft-deleted accounts, causing
dashboard crashes when accessing user properties. This adds a null check
and returns a proper 404 response.
 
Found while investigating SENTRY-5678.
 
Fixes SENTRY-5678

Refactor PR

Extract validation logic to shared module
 
Moves duplicate validation code from the alerts, issues, and projects
endpoints into a shared validator class. No behavior change.
 
This prepares for adding new validation rules in SENTRY-9999 without
duplicating logic across endpoints.

Report actual completed validation and material pending checks/reviews; never omit failures to satisfy a style preference. Verify upstream base/fork head and full committed SHA, then re-read the created PR to confirm its target and content.

Issue References

Reference issues in the PR body:

Guidelines

• One PR per feature/fix - Don't bundle unrelated changes
• Keep PRs reviewable - Smaller PRs get faster, better reviews
• Explain the why - Code shows what; description explains why
• Mark WIP early - Use draft PRs for early feedback

Editing Existing PRs

If you need to update a PR after creation, use gh api instead of gh pr edit:

# Update PR description
gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER -f body="$(cat <<'EOF'
Updated description here
EOF
)"
 
# Update PR title
gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER -f title='new: Title here'
 
# Update both
gh api -X PATCH repos/{owner}/{repo}/pulls/PR_NUMBER \
  -f title='new: Title' \
  -f body='New description'

Use the installed CLI capability/error evidence: historical Projects-classic failures do not establish that gh pr edit is currently broken. API patching remains an alternative.

References

• Sentry Code Review Guidelines
• Sentry Commit Messages

Limitations

• 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.