create-pr

Create pull requests with gh across branches and return the PR URL.

14|1|Updated Dec 29, 2011
One-click install
npx skills add https://github.com/doitian/dotfiles-public --skill create-pr-doitian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/doitian/dotfiles-public/tree/main/ai/skills/create-pr
Command: npx skills add https://github.com/doitian/dotfiles-public --skill create-pr-doitian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and management of pull requests by orchestrating git and GitHub CLI tasks, reducing manual PR overhead.

Core Features & Use Cases

  • Automated PR drafting: Generates a concise PR title and body from the change set and commit history.
  • Parallel state analysis: Checks branch divergence, staged/unstaged changes, and diffs to surface accurate PR scope before creation.
  • Workflow integration: Supports base/target branches, labels, and checks, ensuring PRs align with project standards, with AI-generated summaries when appropriate.

Quick Start

Draft a PR title and body for the current branch and open the PR using gh.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automatically generate a pull request title and body from git commits?

You can automatically generate a pull request title and body by analyzing all commits and diffs in the current branch. This process reviews the change history to draft a concise summary and creates the PR using the gh CLI.

What's the best way to create a pull request across different branches using gh?

Creating a pull request across branches with gh involves analyzing branch divergence and diffs to determine the scope. It pushes your changes to the remote, sets the target base branch, and returns the PR URL upon creation.

Does this PR automation approach work with staged and unstaged git changes?

Yes, PR automation works with staged and unstaged changes by performing parallel state analysis. It checks branch divergence and working tree status to surface accurate PR scope before pushing and creating the request.

Can I add labels and checks to an automated pull request?

Yes, you can add labels and checks to an automated pull request. The workflow supports base and target branch configurations along with project standards, ensuring the PR aligns with repository requirements during creation.

Why does my pull request creation fail when the branch is not pushed to the remote?

Pull request creation fails because the local branch must exist on the remote repository first. The automated workflow handles this by pushing your current branch to the remote before executing the gh command to open the PR.