git-pr-create

Create a GitHub pull request from the current branch with formatted description.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tatsushige-i/shared-claude-code --skill git-pr-create-tatsushige-i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-pr-create
Source: https://github.com/tatsushige-i/shared-claude-code/tree/main/docs/ja-JP/skills/git-pr-create
Command: npx skills add https://github.com/tatsushige-i/shared-claude-code --skill git-pr-create-tatsushige-i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create GitHub PRs from the current branch without manual steps, ensuring proper review alignment and PR formatting.

Core Features & Use Cases

  • Automates PR creation from the active branch, including checks for existing PRs and main-branch guardrails.
  • Analyzes changes to decide if a PR should be created, and generates a well-structured PR description.
  • Use Case: When you're on a feature branch and want to open a PR with a consistent template, checks, and auto-push

Quick Start

Run the PR creation workflow on the current branch to automatically generate and push a PR.

Frequently Asked Questions about git-pr-create

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

FAQPage Schema
How do I automatically create a GitHub pull request from my current branch?

To automatically create a pull request, run the workflow on your active feature branch. It pushes the branch when required, analyzes changes, checks PR size, and generates a well-structured PR description without manual steps.

What is the best way to prevent duplicate pull requests when automating GitHub workflows?

The best way to prevent duplicate pull requests is to use an automated workflow that identifies existing open PRs before creating a new one. This ensures proper review alignment and avoids redundant PR generation for the same branch.

How does PR size analysis work when generating a pull request?

PR size analysis works by evaluating the changes in your current branch before generating a pull request. It assesses the modifications to decide if a PR should be created and ensures the resulting description accurately reflects the scope of changes.

Can I auto-push my feature branch and generate a PR description at the same time?

Yes, you can auto-push your feature branch and generate a PR description simultaneously. The automated workflow pushes the branch when required and immediately creates a properly formatted pull request based on the analyzed changes.

Does this workflow include guardrails to prevent creating PRs directly from the main branch?

Yes, the workflow includes main-branch guardrails to prevent accidental PR creation from the main branch. It analyzes your active branch and ensures pull requests are only generated from appropriate feature branches.