github-pr-create

Creates a GitHub Pull Request from the current branch with auto-generated title and description.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/mjun0812/skills --skill github-pr-create-mjun0812
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-create
Source: https://github.com/mjun0812/skills/tree/main/skills/github/github-pr-create
Command: npx skills add https://github.com/mjun0812/skills --skill github-pr-create-mjun0812

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a good Pull Request is repetitive and error-prone: you must pick the right base branch, summarize the diff accurately, follow the repository's PR template, link related issues, and attach labels. This Skill automates the entire flow from the current branch to a published PR. ## Core Features & Use Cases - End-to-end PR creation: Checks branch and commit readiness, pushes to remote, generates a Conventional Commits title, and creates the PR via gh pr create with assignee, labels, and image attachments. - Template- and language-aware body generation: Follows the repository's own PR template when present, otherwise uses bundled English or Japanese templates, with strict writing-style rules per language. - Smart context detection: Infers the correct base branch (including stacked PRs), links related issues via Closes, and supports a --dry-run mode to preview everything without pushing. - Use Case: After finishing a feature branch, simply ask for a PR and get a fully formatted, template-compliant Pull Request with linked issues, labels, and embedded diagrams or screenshots. ## Quick Start Create a pull request from my current branch in Japanese using the repository's PR template.

Frequently Asked Questions about github-pr-create

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

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

Ask the assistant to create a PR and it will push the branch, generate a Conventional Commits title and template-based body from the diff, then run gh pr create with assignee, labels, and attachments. You can optionally specify the language or a related issue number.

How to generate a PR description from git diff automatically?

The skill reads the commit list and diff between origin/<base> and HEAD, then writes the body following the repository's PR template or bundled English/Japanese templates. It never writes from memory, so the description always matches the actual changes.

Can I preview a pull request before creating it on GitHub?

Yes, pass the --dry-run argument to see the generated title, body, base/head branches, and any diagram or image placements locally. No push, upload, or gh pr create is executed in dry-run mode.

Does gh pr create support image attachments in the PR body?

Yes, gh CLI v2.99.0 or later supports the --attach flag to upload images referenced in the body file. It requires write permission to the repository and does not work on GitHub Enterprise Server.

What happens if my branch already has an open pull request?

The skill checks for an existing PR on the current branch before doing anything. If one exists, it displays the PR URL and status, then stops instead of creating a duplicate.

How is the base branch chosen for stacked pull requests?

If unrelated commits appear between origin/<base> and HEAD, the skill looks for an open PR whose head branch the current branch is stacked on and uses that as the base. When ambiguous, it asks you to confirm the candidate branches.