create-pull-request

Create GitHub pull requests from local Git history using the gh CLI.

820|64|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/warpdotdev/oz-skills --skill create-pull-request-warpdotdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/warpdotdev/oz-skills/tree/main/.agents/skills/create-pull-request
Command: npx skills add https://github.com/warpdotdev/oz-skills --skill create-pull-request-warpdotdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating well-structured GitHub pull requests, ensuring adherence to project conventions and best practices, thereby saving developers time and reducing manual errors.

Core Features & Use Cases

  • Automated Context Gathering: Analyzes commits, branches, and diffs to understand the scope of changes.
  • Intelligent Title Generation: Creates descriptive PR titles using Conventional Commits or a clear summary.
  • Prerequisite Checks: Verifies gh CLI installation, authentication, and the existence of related skills.
  • Use Case: When you've finished a feature on a new branch and want to submit it for review, this Skill will guide you through creating a PR with a relevant title and description, checking for existing PRs, and ensuring your branch is up-to-date.

Quick Start

Use the create-pull-request skill to open a pull request for your current branch.

Frequently Asked Questions about create-pull-request

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

FAQPage Schema
How do I automate GitHub pull request creation from local Git history?

Automating GitHub pull request creation involves analyzing local Git history and project conventions to gather context. The tool checks prerequisites, generates intelligent titles and descriptions from commits and diffs, and leverages the `gh` CLI for PR submission.

Can I use conventional commits to generate my pull request title automatically?

Yes, you can use conventional commits to generate pull request titles automatically. The automation reads your commit history and project conventions to create descriptive PR titles that adhere to standard formats, ensuring clear and structured summaries for code review.

Do I need the GitHub CLI installed to automate pull request submission?

Yes, the GitHub CLI (`gh`) is required to automate pull request submission. The tool performs prerequisite checks to verify `gh` CLI installation and authentication before gathering context and submitting your PR.

How does automated PR context gathering work with existing project conventions?

Automated PR context gathering analyzes local commits, branches, and diffs to understand the scope of changes. It integrates with existing PR templates and project conventions to ensure the generated description accurately reflects your developer workflow.

What prerequisite checks are needed before creating a GitHub pull request?

Before creating a GitHub pull request, prerequisite checks include verifying `gh` CLI installation, confirming authentication status, and checking for related skills. These checks ensure your branch is ready and the PR submission process will execute without manual errors.

What's the best way to streamline a developer workflow for submitting code reviews?

The best way to streamline a developer workflow for code reviews is to automate PR creation. By analyzing Git diffs and leveraging the `gh` CLI, the tool generates relevant titles and descriptions, reducing manual effort and ensuring adherence to project best practices.