create-pr

Create standardized draft pull requests with GitHub CLI following Sentry conventions.

12|1|Updated Apr 3, 2024
One-click install
npx skills add https://github.com/getsentry/webvitals.com --skill create-pr-getsentry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/getsentry/webvitals.com/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/getsentry/webvitals.com --skill create-pr-getsentry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of pull requests that adhere to Sentry's engineering practices, reducing manual PR setup and ensuring consistent review-ready descriptions.

Core Features & Use Cases

  • PR hygiene and automation: verifies branch state, analyzes changes, and prepares standardized PR descriptions per guidelines.
  • Standardized PR creation: uses GitHub CLI to create draft PRs with template formats suitable for code review.
  • Use Case: When working across multiple commits or branches, this Skill ensures PRs meet code review guidelines and are ready for review.

Quick Start

Draft and open a PR that follows Sentry conventions using the gh pr create workflow.

Frequently Asked Questions about create-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate pull request creation to follow consistent branch hygiene and structured descriptions?

To automate standardized pull request creation, this process verifies branch state and analyzes changes to draft structured descriptions. It then uses GitHub CLI to create draft PRs following template conventions for code review.

Can I use GitHub CLI to generate draft PRs that follow Sentry conventions?

Yes, GitHub CLI can generate draft PRs following Sentry conventions by using gh pr create with a template. This enforces branch hygiene, commit validation, and structured descriptions for code review.

What is the best way to ensure my commits pass validation before opening a pull request?

The best way to ensure commits pass validation before opening a pull request is to use an automated workflow that verifies branch state and analyzes changes. This enforces commit validation prior to drafting the PR.

Does this PR automation workflow work across multiple branches and commits?

Yes, this PR automation workflow works across multiple branches and commits. It analyzes changes and prepares standardized descriptions to ensure PRs meet code review guidelines regardless of branch state.

How do I structure PR descriptions for code review using a template?

To structure PR descriptions for code review, use a template format to ensure consistency. The workflow analyzes changes and drafts the description automatically before opening the PR via GitHub CLI.