create-pr

Generate a Japanese PR title and body from commit history and create it with gh pr create.

Updated Jul 10, 2025
One-click install
npx skills add https://github.com/junkisai/dotfiles --skill create-pr-junkisai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/junkisai/dotfiles/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/junkisai/dotfiles --skill create-pr-junkisai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates creating GitHub PRs by analyzing the current branch's commit history and generating a Japanese title and body, then submitting the PR via gh pr create.

Core Features & Use Cases

  • Read the commit history to produce a concise, context-aware PR title in Japanese.
  • Generate a detailed PR body from commit messages using a structured template.
  • Create a PR on GitHub with the appropriate base branch, handling single or multiple commits and guiding the user through required steps (e.g., pushing to remote).

Quick Start

Create a PR from the current branch by reading the commit history and generating a Japanese title and body, then open it with gh pr create.

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 GitHub pull request from my commit history?

Automating PR creation from commit history involves reading the branch diff, generating a context-aware title and structured body from commit messages, and submitting the PR via the gh pr create command to the default base branch.

Can I generate a Japanese PR title and body automatically from my commits?

Generating a Japanese PR title and body automatically requires analyzing commit messages to produce a concise title and structured body, which are then applied directly to the pull request creation workflow.

What is the best way to create a PR from multiple commits without manual formatting?

Creating a PR from multiple commits without manual formatting is achieved by reading the collective commit history, applying a structured template to generate the body, and executing the pull request creation command with the appropriate base branch.

Do I need to push my branch to remote before creating a pull request with this automation?

Pushing your branch to remote is a prerequisite step before creating a pull request, as the automation workflow requires the commits to be on the remote to successfully execute the PR creation command.

How does the pull request automation handle the base branch selection?

Handling base branch selection in PR automation involves reading the diff between the base and head branches, then configuring the pull request creation command to target the appropriate default base branch automatically.

What are the limitations of using commit history to auto-generate PR titles?

Limitations of auto-generating PR titles from commit history include the 70-character maximum length constraint for the title, requiring the diff analysis to produce highly concise summaries while maintaining context awareness.