skills.rest
zuzu59
zuzu59COMMUNITY
Explore all skills by this author →
GitHub

create-pr

Generate pull request titles and bodies from local changes via GitHub CLI.

Updated Jun 1, 2026
Search Tags:#automation#git#workflow#code-review#pull-request#pr-creation
One-click install
npx skills add https://github.com/zuzu59/z-skills --skill create-pr-zuzu59
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/zuzu59/z-skills/tree/main/skills/create-pr
Command: npx skills add https://github.com/zuzu59/z-skills --skill create-pr-zuzu59

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual PR creation is error-prone and time-consuming, especially when balancing descriptive titles with useful bodies during busy development cycles. This skill automates the end-to-end PR workflow from a feature branch, ensuring consistent messaging and quick reviews.

Core Features & Use Cases

  • Auto-generate a concise PR title from the most recent commits or changes.
  • Compose a meaningful PR body with bullet-point highlights for easy review.
  • Enforce branch-safety rules (auto-detect main/master, prompt for a new branch if needed) and submit PRs via GitHub CLI.

Quick Start

Create a pull request from your current branch with an auto-generated title and description.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from a feature branch?▼

You can automate pull request creation by generating a concise title and body from local changes, then submitting them directly via the gh pr create command. This workflow ensures consistent messaging and pushes your changes to the origin remote.

Can I automatically generate a PR title and body from my local git commits?▼

Yes, automated PR generation builds a concise title and a meaningful bullet-point body directly from your recent commits or local changes. This ensures quick reviews and consistent messaging without manual formatting.

Does this PR workflow prevent committing directly to the main branch?▼

Yes, the workflow enforces branch-safety rules by auto-detecting if you are on the main or master branch. It will prompt you to create a new feature branch before proceeding with any commits or PR submission.

What is the best way to ensure consistent PR descriptions during busy development cycles?▼

Automating your PR workflow is the best way to ensure consistent descriptions, as it composes meaningful PR bodies with bullet-point highlights and enforces branch-safety rules to prevent errors during busy development cycles.

Do I need the GitHub CLI installed to submit automated pull requests?▼

Yes, you need the GitHub CLI installed because the workflow submits pull requests and returns the PR URL using the gh pr create command after pushing your local changes to the origin.

Why does my automated PR workflow prompt for a new branch?▼

The automated PR workflow prompts for a new branch because it enforces branch-safety rules by auto-detecting main or master, ensuring you never accidentally push local changes directly to protected branches.

Related Skills

Explore More Software Engineering Skills→
PiklarPiklar

speckit-git-remote

Detect and parse Git remote origin URLs to identify GitHub repository ownership.

Community
Basic
matt-rileymatt-riley
1

review-comment-resolution

Classify PR review comments and apply validated fixes to code branches.

Community
Intermediate
gihwan-devgihwan-dev
1

commit

Generate conventional commit messages for staged and unstaged Git changes.

Community
Intermediate
minusfiveminusfive
5

pr-guidelines

Enforce project-specific Git guidelines for branch pushes and pull requests.

Community
Basic