skills.rest
kkhys
kkhysCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

creating-pr

Create GitHub pull requests with standardized titles and draft status.

1|Updated Jan 10, 2026
Search Tags:#automation#workflow#github#pr#draft#pull-request#conventional-commits
One-click install
npx skills add https://github.com/kkhys/claude-code-marketplace --skill creating-pr-kkhys
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: creating-pr
Source: https://github.com/kkhys/claude-code-marketplace/tree/main/plugins/base/skills/creating-pr
Command: npx skills add https://github.com/kkhys/claude-code-marketplace --skill creating-pr-kkhys

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

PR creation is error-prone when titles are inconsistent and body descriptions lack structure, leading to review friction and delays.

Core Features & Use Cases

  • Enforces standardized PR titles in the form [base-branch] type: description
  • Generates concise bullet-point PR descriptions from code changes
  • Supports creating draft PRs and assigns the PR to a user automatically

Quick Start

Create a draft PR for the current branch using a standardized title and a concise bullet-point description.

Frequently Asked Questions about creating-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with consistent titles?▼

Automating GitHub pull request creation requires enforcing standardized title formats using the base branch, a Conventional Commits type, and a concise description. This ensures consistent messaging and reduces review friction across main and development workflows.

How do I create a draft pull request with an auto-generated body?▼

Creating a draft pull request with an auto-generated body involves analyzing code changes to produce concise bullet-point descriptions. The PR is automatically set to draft status and assigned to a user, streamlining the preparation process from feature branches.

What is the standard format for conventional commit pull request titles?▼

The standard format for conventional commit PR titles combines the base branch, commit type, and a short description into the pattern [base-branch] type: description. This structure ensures titles are uniform and easily parseable.

Can I automatically assign a pull request to a user when creating a draft?▼

Automatically assigning a pull request to a user during draft creation is supported. The workflow generates the draft PR with a structured body and ensures it is immediately assigned to the appropriate user without manual intervention.

Does this PR automation work with both main and development branch workflows?▼

This PR automation works effectively with both main and development branch workflows. It deduces the commit type and formats the title based on the specific base branch targeted by the feature branch, ensuring consistent messaging across different environments.

Why are inconsistent pull request titles a problem for code reviews?▼

Inconsistent pull request titles and unstructured body descriptions cause review friction and delays. Standardizing titles and generating concise bullet-point bodies from code changes resolves this by providing clear, uniform context for reviewers.

Related Skills

Explore More Software Engineering Skills→
JoNaYeonJoNaYeon
1

work_git_pr-creator

Create GitHub pull requests with descriptions from local branch changes.

Community
Intermediate
gesmith0606gesmith0606

gsd-ship

Push branches and create pull requests with auto-generated bodies and reviewer assignment.

Community
Intermediate
MuvonMuvon
3

git-workflow

Standardize Git commit messages, branch names, and history workflows.

Official
Basic
rickypowellrickypowell
1

Using `gh` commands on the command line, bash, or zsh

Use GitHub CLI commands in bash or zsh with --body-file for multi-line text.

Community
Basic