create-pr

Create standardized GitHub pull requests with Conventional Commit titles and templates.

9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/paultyng/skill-issue --skill create-pr-paultyng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/paultyng/skill-issue/tree/main/skills/create-pr
Command: npx skills add https://github.com/paultyng/skill-issue --skill create-pr-paultyng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually creating GitHub pull requests often leads to inconsistent formatting, missed team template requirements, and non-standard titles that don't follow agreed-upon conventions like Conventional Commits. This skill removes that repetitive manual work and ensures every PR aligns with your repository's standards.

Core Features & Use Cases

  • Auto PR Template Detection: Automatically locates and uses the first matching pull request template from common repository paths, with fallback logic for case-insensitive file matching and multiple template selection based on commit type.
  • Conventional Commit Title Generation: Creates compliant PR titles directly from your branch's commit history, synthesizing a single title for multiple related commits.
  • Precondition Validation: Confirms your branch is pushed to a remote and no open PR already exists for the branch before attempting creation, following team rules for draft PRs by default.
  • Use Case: A developer who just finished a feature branch can use this skill to instantly generate a properly formatted draft PR with the correct title and template content, no manual copy-pasting or formatting required.

Quick Start

Use the create-pr skill to open a draft pull request for your current branch using the repo's existing pull request template.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with conventional commit titles?

Automating GitHub pull request creation generates compliant PR titles directly from your branch's commit history, synthesizing multiple related commits into a single standardized title. This removes manual formatting and ensures conventional commit compliance.

How do I ensure my pull request uses the correct repository PR template automatically?

Automatic PR template detection locates and applies the first matching pull request template from common repository paths using case-insensitive fallback logic. This ensures your PR adheres to team formatting standards without manual copy-pasting.

Can I create a draft pull request by default for my feature branch?

Yes, you can create a draft pull request by default for your feature branch. The process follows team rules for draft PRs to ensure standardized code review workflows before merging changes.

What preconditions are checked before opening a pull request on a remote branch?

Precondition validation confirms your branch is pushed to a remote repository and verifies no open pull request already exists for that branch. This prevents duplicate PRs and failed creation attempts.

What is the best way to handle multiple conventional commits when generating a PR title?

The best way to handle multiple conventional commits is synthesizing them into a single compliant PR title generated from the branch's commit history. This ensures the title accurately represents all related changes without manual summarization.