create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentrys code review guidelines.
Security Assessment
About create-pr
The 'create-pr' skill is designed to facilitate the creation of pull requests (PRs) that adhere to Sentry's engineering conventions. It addresses the common challenges developers face when preparing changes for review, ensuring that the process is streamlined and compliant with best practices. By following a structured approach, this skill helps maintain code quality and enhances collaboration within teams, reducing the likelihood of errors and miscommunication during code reviews.
This skill offers several key features, including the ability to verify branch states, analyze changes before submission, and create PRs with well-structured descriptions. It guides users through a step-by-step process that includes checking for uncommitted changes, understanding the scope of modifications, and utilizing templates for PR descriptions. Additionally, users can easily request reviews from team members, which fosters accountability and ensures that the right people are involved in the review process.
The target users for this skill are developers working in teams that utilize GitHub for version control and wish to improve their pull request workflow. It is particularly useful for those who need to adhere to specific coding standards and want to ensure that their PRs are clear, concise, and informative. This skill is ideal for both new contributors looking to understand the PR process and experienced developers aiming to enhance their efficiency in code reviews.
FAQ
What do I need to use the create-pr skill?
You need to have the GitHub CLI ('gh') authenticated and available.
What should I do if I have uncommitted changes?
Run the 'sentry-skills:commit' skill to commit your changes before creating a PR.
Can I use this skill without a PR template?
Yes, if a PR template does not exist, you can follow the provided structure for writing your PR description.
How many reviewers should I add to my PR?
It is recommended to limit the number of reviewers to 1-3 to maintain clear ownership.
What format should I use for the PR title?
The title should follow commit conventions, such as 'feat(scope): Add new feature' or 'fix(scope): Fix the bug'.
Install create-pr
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
getsentry/skills