Agent skill · writing content · aiskillstore
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
Why this skill is useful
Adds specific PR creation commands and structured description templates that align with Sentry's conventions, which the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Create Pull Request Create pull requests following Sentry's engineering practices. When to Use This Skill Use this skill when: Opening pull requests Writing PR descriptions Preparing changes for review Following Sentry's code review guidelines Creating PRs that follow best 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. 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 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: Understand the scope and purpose of all changes before writing the description. Step 3: Write the PR Description Use this structure for PR descriptions (ignoring any repository PR templates): 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 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 Title format follows commit conventions: feat(scope): Add new feature fix(scope): Fix the bug ref: Refactor something PR Description Examples Feature PR Bug Fix PR Refactor PR Issue References Reference issues in the PR body: Syntax Effect -------- -------- Fixes #1234 Closes GitHub issue on merge Fixes SENTRY-1234 Closes Sentry issue Refs GH-1234 Links without closing Refs LINEAR-ABC-123 Links Linear issue 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 draf …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/create-pr--5cda1c