skills.rest
shuymn
shuymnCOMMUNITY
Explore all skills by this author →
Website𝕏@shuymnGitHub

create-pr

Create GitHub pull requests from committed changes with optional flags.

1|Updated Mar 8, 2015
Search Tags:#automation#git#github#code-review#pull-request#development-workflow
One-click install
npx skills add https://github.com/shuymn/dotfiles --skill create-pr-shuymn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/shuymn/dotfiles/tree/main/etc/claude/skills/create-pr
Command: npx skills add https://github.com/shuymn/dotfiles --skill create-pr-shuymn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review committed changes and streamline the PR creation process on GitHub, reducing manual steps and ensuring consistent PR descriptions.

Core Features & Use Cases

  • Create PRs from the current feature branch to the repository's base branch.
  • Update an existing PR with new commits and descriptions.
  • Supports --japanese flag for Japanese PR descriptions and --base to specify the target branch.
  • Works with the GitHub MCP server to submit PRs using a standardized workflow.

Quick Start

Create a pull request from the current branch to the default base branch, optionally using --base, --update, and --japanese flags.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation from local commits?▼

Automating GitHub pull request creation from local commits involves executing an end-to-end workflow that converts committed changes into standardized PRs. This Skill applies standard PR templates to generate consistent titles and bodies using the GitHub MCP server.

Can I update an existing PR with new commits instead of creating a new one?▼

Updating an existing PR with new commits is supported using the --update flag. This modifies the current pull request by appending new commits and refreshing the PR description without opening a duplicate request on GitHub.

How do I specify a target base branch when creating a pull request?▼

Specifying a target base branch when creating a pull request is done using the --base flag. This directs the PR workflow to target a specific branch instead of the repository's default base branch.

Does this PR automation workflow support generating Japanese descriptions?▼

Generating Japanese PR descriptions is supported through the --japanese flag. This configures the workflow to output the pull request title and body in Japanese instead of the default language.

Do I need the GitHub MCP server to submit pull requests with this workflow?▼

The GitHub MCP server is required to submit pull requests with this workflow. It integrates with the server to execute the end-to-end PR creation process and apply standard PR templates for consistent formatting.

What is the best way to ensure consistent PR descriptions across a development workflow?▼

Ensuring consistent PR descriptions across a development workflow is achieved by applying standard PR templates during automated creation. This generates uniform titles and bodies for every pull request submitted via the GitHub MCP server.

Related Skills

Explore More Software Engineering Skills→
tomholfordtomholford
6

push

Stage, commit, and push changes to a Git repository.

Community
Intermediate
qvidal01qvidal01

ship

Automate CI/CD merge and deployment for GitHub pull requests.

Community
Advanced
RyoMurakami1983RyoMurakami1983
2

git-initial-setup

Automates GitLab project and repository setup for streamlined onboarding and management.

Community
Intermediate
tranhieutttranhieutt
70

pr-writer

Generate GitHub pull request titles and bodies following conventional commit conventions.

Community
Intermediate