create-pr

Draft a GitHub pull request describing net branch changes.

8|1|Updated Mar 9, 2019
One-click install
npx skills add https://github.com/wangl-cc/dotfiles --skill create-pr-wangl-cc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/wangl-cc/dotfiles/tree/main/home/dot_agents/skills/create-pr
Command: npx skills add https://github.com/wangl-cc/dotfiles --skill create-pr-wangl-cc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Draft and describe a GitHub pull request that accurately communicates the net changes from the current branch, avoiding ambiguity from individual commits.

Core Features & Use Cases

  • Targeted PR creation: Generate a concise PR title and body that reflect the end state relative to the target branch.
  • Flexible targets: Default to main but support specifying another target branch.
  • PR governance: Detect existing PRs for the branch and offer to update instead.

Quick Start

Ask the system to create a PR from the current branch to the target branch (default main) with a title and body describing the net changes.

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 pull request from my current Git branch to main?

To create a pull request, the Skill drafts a GitHub PR from your current branch by checking the diff against the target branch and generating a formatted title and body describing the net changes.

Do I need the gh CLI installed and authenticated to automate GitHub PR creation?

Yes, GitHub PR creation requires the gh CLI to be installed and authenticated, as the Skill relies on it to detect existing PRs and format the net branch changes into a pull request.

Can I specify a target branch other than main when opening a pull request?

Yes, you can specify another target branch for your pull request, although the Skill defaults to main when comparing your current branch diff and drafting the PR body.

What happens if there is an existing pull request for my current branch?

When an existing pull request is detected for your current branch, the Skill offers PR governance by proposing to update the existing PR instead of creating a duplicate request.

How does this pull request generator handle multiple ambiguous commits?

The pull request generator avoids ambiguity from individual commits by analyzing the net changes from the current branch against the target, formatting a concise PR title and body that accurately reflects the end state.

What's the best way to draft a PR title and body for GitHub branch management?

The best way to draft a PR title and body is using automated branch diff detection, which summarizes the net changes from your current branch against main into a clear, concise GitHub pull request.