create-pr

Create pull requests from the current branch to a base branch using the GitHub CLI.

1|Updated Oct 13, 2022
One-click install
npx skills add https://github.com/kryota-dev/dotfiles --skill create-pr-kryota-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/kryota-dev/dotfiles/tree/main/.bin/.claude/skills/create-pr
Command: npx skills add https://github.com/kryota-dev/dotfiles --skill create-pr-kryota-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the creation of pull requests from the current branch, reducing manual steps and potential errors in PR preparation.

Core Features & Use Cases

  • Automatic analysis of the current branch against the target base branch to identify changes.
  • Draft PR generation with a template-driven body and a consistent title, ready to review.
  • GitHub CLI integration to create or update PRs, verify existing PRs, and post drafts for collaboration.

Quick Start

Create a draft PR from the current branch to the specified base branch using the GitHub CLI.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from a feature branch to a base branch?

You can automate pull request creation by using the GitHub CLI to analyze the diff between your current feature branch and a specified base branch, then generate a draft PR with a consistent title and body.

Does automated PR generation work with existing repository PR templates?

Yes, automated PR generation populates the PR body directly from your repository's PR template, ensuring that the generated draft adheres to your project's established documentation and review standards.

How do I check for existing pull requests before creating a new one?

The automation workflow checks for existing pull requests on your branch before creating a new one, preventing duplicate PRs and allowing it to update or post drafts for ongoing collaboration seamlessly.

Do I need GitHub CLI authentication to create draft PRs automatically?

Yes, proper GitHub CLI authentication is required to automate end-to-end PR creation, allowing the system to verify branch access, analyze diffs, and push draft pull requests to your repository.

Can I generate a draft PR automatically instead of publishing it directly?

Yes, the automation process generates draft pull requests by default, applying template-driven bodies and consistent titles so your changes are ready for review before final publication.

What is the best way to analyze a branch diff before opening a GitHub pull request?

The best way to analyze a branch diff is through an automated GitHub CLI workflow that compares the current branch against the target base branch, using the results to generate the PR title and body.