Create Pr

If you work in a Sentry codebase, this wraps the GitHub CLI to enforce their PR conventions: conventional commit titles, descriptions that explain motivation over test plans, and proper issue references. It walks you through verifying your branch state, analyzing the diff, and writing a description that actually helps reviewers understand why you made these changes. The examples are pulled straight from Sentry's internal guidelines, so you get the feat/fix/ref prefixes right and skip the checkbox theatre they explicitly don't want. Useful if you're contributing to Sentry or want to adopt similar conventions for your own team.

skills.sh installs: 314
GitHub stars: 33.2K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add davila7/claude-code-templates --skill create-pr --agent claude-code

Installs into .claude/skills of the current project.

Files

Create Pull Request

Create pull requests following Sentry's engineering practices.

Requires: GitHub CLI (gh) authenticated and available.

Process

Step 1: Verify Branch State

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

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

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