← ClaudeAtlas

create-prlisted

Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
aiskillstore/marketplace · ★ 334 · Code & Development · score 80
Install: claude install-skill aiskillstore/marketplace
# Create Pull Request Create pull requests following Sentry's engineering practices. **Requires**: GitHub CLI (`gh`) authenticated and available. ## 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 # Check current branch and status git status git log main..HEAD --oneline ``` Ensure: - All changes are committed - Branch is up to date with remote - Changes are rebased on main if needed ### Step 2: Analyze Changes Review what will be included in the PR: ```bash # See all commits that will be in the PR git log main..HEAD # See the full diff git diff main...HEAD ``` Understand the scope and purpose of all changes before writing the description. ### Step 3: Write the PR Description Follow this structure: ```markdown <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> ``` **Do NOT include:** - "Test plan" sections - Checkbox lists of testing steps - Redundant summaries of the diff **Do include:** - Clear explanation of what and why - Links