Skills create-pr
📦

create-pr

Safe ⚙️ External commands

Create pull requests with Sentry-compliant descriptions

Also available from: Cygnusfear,0tarof,davila7,Cloud-Officer,getsentry,Crearize,0tarof

Writing effective PR descriptions that follow team conventions takes time and consistency. This skill automates PR creation using GitHub CLI with Sentry's proven review guidelines.

Supports: Claude Codex Code(CC)
📊 70 Adequate
1

Download the skill ZIP

2

Upload in Claude

Go to Settings → Capabilities → Skills → Upload skill

3

Toggle on and start using

Test it

Using "create-pr". User has commits adding Slack thread notification feature

Expected outcome:

Created draft PR: 'feat(alerts): Add Slack thread replies for notifications'

PR Description:
- Explains threading behavior vs message edits
- Documents timeline preservation benefit
- References SENTRY-1234

Using "create-pr". User fixed null handling crash in API endpoint

Expected outcome:

Created draft PR: 'fix(api): Handle null response in user endpoint'

PR Description:
- Describes crash scenario
- Explains null check implementation
- Links to investigation ticket SENTRY-5678

Security Audit

Safe
v1 • 2/24/2026

Static analysis flagged 36 external command patterns and 3 network references, but all are false positives. The skill uses GitHub CLI (gh) and git commands with hardcoded arguments for legitimate PR creation. Network references are documentation URLs only. No user input injection vectors or data exfiltration risks detected.

1
Files scanned
193
Lines analyzed
1
findings
1
Total audits
Audited by: claude

Quality Score

38
Architecture
100
Maintainability
87
Content
22
Community
100
Security
91
Spec Compliance

What You Can Build

Feature Development PR

Create a PR for a new feature with clear motivation, alternative approaches considered, and relevant issue references.

Bug Fix PR

Quickly create a focused bug fix PR that explains the root cause, the fix, and links to the tracking issue.

Refactoring PR

Document code reorganization with before/after context and explain why the refactor enables future work.

Try These Prompts

Create a basic PR
Create a pull request for my current branch. Analyze the changes and write a description following Sentry conventions.
Feature PR with context
I've implemented feature X. Create a PR that explains what the feature does, why it was needed, and any trade-offs considered.
Bug fix with issue link
Create a PR for this hotfix. Make sure to include 'Fixes SENTRY-1234' so the issue closes automatically on merge.
Large refactor documentation
Create a PR for this refactoring. Emphasize that there are no behavior changes and explain what motivated the reorganization.

Best Practices

  • Keep PRs focused on a single feature or fix for faster reviews
  • Explain the 'why' behind changes, not just what the code does
  • Use draft PRs early when you want feedback on incomplete work

Avoid

  • Bundling unrelated changes into one large PR
  • Writing vague titles like 'Update code' or 'Fix stuff'
  • Skipping the PR description entirely and leaving reviewers to guess

Frequently Asked Questions

What do I need before using this skill?
You need GitHub CLI (gh) installed and authenticated with `gh auth login`. All your changes should also be committed before creating a PR.
Does this skill work with non-GitHub repositories?
No, this skill is specifically designed for GitHub repositories and uses the GitHub CLI (gh) which only works with GitHub.
What happens if I have uncommitted changes?
The skill will detect uncommitted changes and prompt you to run the commit skill first. PRs should only include committed changes.
Can this skill update an existing PR?
Yes, the skill can update existing PRs using the GitHub API directly, which is more reliable than gh pr edit for certain operations.
What PR title format does this use?
Conventional commits format: 'type(scope): description'. Examples: 'feat(auth): Add OAuth support' or 'fix(api): Handle timeout errors'.
Does this automatically select reviewers?
No, this skill focuses on PR creation and description. Reviewer selection should be done manually based on team processes.

Developer Details

File structure

📄 SKILL.md