github-pr

Generate a pull request with an English title and Japanese description from branch changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sunbluesome/dotfiles --skill github-pr-sunbluesome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/sunbluesome/dotfiles/tree/main/.claude/ds/skills/github-pr
Command: npx skills add https://github.com/sunbluesome/dotfiles --skill github-pr-sunbluesome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps developers streamline PR creation by automatically generating an English title and a Japanese description derived from the current branch's changes.

Core Features & Use Cases

  • Generate a concise English PR title and a Japanese description based on commit history since branching from main, changed files and their diffs, and branch naming conventions.
  • Summarize branch changes for PRs to improve code-review efficiency.
  • Use when you want to open a PR from the active branch without manual drafting.

Quick Start

Create a PR for the current branch with an English title and Japanese description.

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I generate a pull request from a current git branch automatically?

To generate a pull request from a current git branch, this skill analyzes commit history since branching, changed files, and diffs to produce an English title and Japanese description automatically.

Can I create a bilingual GitHub PR title and description from recent commits?

Yes, you can create a bilingual GitHub PR by using this skill to summarize branch changes into an English title and a Japanese description based on recent commits and file diffs.

Does this pull request generator require a specific base branch like main?

This pull request generator requires a git context with a base main branch to accurately analyze commit history since branching and generate the PR title and description.

What is the best way to summarize branch diffs for code review?

The best way to summarize branch diffs for code review is to automatically extract changed files and commit history to generate a structured PR description, improving review efficiency.

How does branch naming convention affect the generated PR title and description?

Branch naming conventions are analyzed alongside commit history and diffs to generate a concise English PR title and Japanese description that accurately reflects the branch changes.

Why does my automated PR description only output in English and Japanese?

The automated PR description outputs in English and Japanese because the skill enforces a specified output format, generating an English title paired with a Japanese description.