create-pr

Create GitHub pull requests with titles matching the <type>(<scope>): <summary> pattern.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/drdanmaggs/rocket-fuel --skill create-pr-drdanmaggs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/drdanmaggs/rocket-fuel/tree/main/internal/plugin/skills/create-pr
Command: npx skills add https://github.com/drdanmaggs/rocket-fuel --skill create-pr-drdanmaggs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of GitHub pull requests with titles that pass the check-pr-title CI validation, reducing manual formatting errors and review delays.

Core Features & Use Cases

  • Enforces the conventional PR title format: <type>(<scope>): <summary>.
  • Integrates with gh CLI to create PRs from the command line and guide branch naming.
  • Supports common PR workflows for features, fixes, and documentation changes.

Quick Start

Describe the PR you want to create by providing type, scope, and summary, and the skill will generate a properly formatted PR title and create the PR.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a GitHub pull request with a CI-compliant title format?

Use the gh CLI to create a pull request with a title matching the <type>(<scope>): <summary> pattern, which passes the check-pr-title CI validation and prevents formatting-related review delays.

What is the conventional PR title format for passing check-pr-title CI validation?

The conventional PR title format is <type>(<scope>): <summary>, where type covers features, fixes, or documentation changes, and scope identifies the affected module to satisfy CI validation checks.

Can I automate pull request creation from the command line using gh CLI?

Yes, the skill uses the gh CLI and Bash-based tooling to scaffold and open pull requests from the command line, guiding branch naming and PR metadata while enforcing the conventional title format.

Does the gh CLI support enforcing conventional commit pull request titles for CI pipelines?

Yes, the gh CLI supports creating pull requests with conventional commit titles by validating the <type>(<scope>): <summary> pattern before submission, ensuring CI pipelines pass the check-pr-title validation.

Why does my pull request title fail check-pr-title CI validation on GitHub?

Pull request titles fail CI validation when they do not match the required <type>(<scope>): <summary> pattern, a formatting issue this skill resolves by automating title generation and validation.

What's the best way to automate GitHub pull request creation for feature branches and bug fixes?

Automate GitHub pull request creation by providing the type, scope, and summary to generate a compliant title and open the PR using the gh CLI, supporting feature branches, bug fixes, and documentation changes.