pr

Create GitHub pull requests with templates, labels, and branch checks.

318|146|Updated Oct 5, 2017
One-click install
npx skills add https://github.com/woocommerce/woocommerce-android --skill pr-woocommerce
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/woocommerce/woocommerce-android/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/woocommerce/woocommerce-android --skill pr-woocommerce

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of creating pull requests by ensuring adherence to project-specific conventions, templates, and labeling standards, reducing review friction and improving code quality.

Core Features & Use Cases

  • Automated Branch Verification: Ensures you are not creating a PR from the main branch.
  • Commit Status Check: Verifies that there are no uncommitted changes before proceeding.
  • Diff Analysis: Provides a summary of changes and commit history for review.
  • PR Template Enforcement: Uses the project's defined PR template for consistent descriptions.
  • Automated Labeling: Suggests and applies relevant labels based on code changes and branch naming.
  • Use Case: After completing a feature, use this Skill to automatically generate a well-formatted pull request with the correct title, body, and labels, ready for review.

Quick Start

Use the pr skill to create a pull request for the current branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate GitHub pull request creation with project-specific templates?

Automating GitHub pull request creation involves enforcing PR title and body formats, verifying branch status, analyzing code diffs, and applying relevant labels. This ensures adherence to project conventions and reduces review friction.

What is the best way to enforce PR title and body formats for code review?

The best way to enforce PR title and body formats is to apply project-specific conventions and templates during pull request generation. This standardizes descriptions, analyzes code diffs, and applies relevant labels for consistent code review.

Can I use GitHub CLI to automatically apply labels based on branch naming?

Yes, you can use GitHub CLI to automatically suggest and apply relevant labels based on code changes and branch naming. This automated labeling integrates directly with PR generation to categorize pull requests efficiently.

Does automated PR generation verify uncommitted changes before proceeding?

Yes, automated PR generation verifies uncommitted changes through a commit status check before proceeding. It also performs automated branch verification to ensure you are not creating a pull request directly from the main branch.

Why does a pull request fail when creating it from the main branch?

A pull request fails when created from the main branch because automated branch verification prevents it. This check ensures feature branches are used, maintaining repository integrity by stopping direct main branch PR generation.

Do I need GitHub CLI to generate compliant pull requests?

Yes, you need GitHub CLI to generate compliant pull requests. The automation supports integration with GitHub CLI specifically for PR generation, diff analysis, and applying relevant labels according to project templates.