pr-writer

npx skills add sickn33/agentic-awesome-skills --skill pr-writer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# 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 available `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 available `commit` skill before proceeding. If the client requires qualified skill names, use the qualifier for the plugin that supplied this skill. ## 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 an

Check for uncommitted changes
git status --porcelain
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
See all commits that will be in the PR (substitute detected branch name for BASE)
git log BASE..HEAD
See the full diff