create-pr

Create GitHub pull requests with standardized titles and summaries via gh pr create.

Updated Jan 22, 2026

Search Tags:#automation #GitHub #review #description #PR #pull-request #title

Ready to run

npx skills add https://github.com/gricha/clawdbot-skills --skill create-pr-gricha

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/gricha/clawdbot-skills/tree/main/create-pr
Command: npx skills add https://github.com/gricha/clawdbot-skills --skill create-pr-gricha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers create pull requests with concise, useful descriptions, reducing review time and back-and-forth.

Core Features & Use Cases

Title guidance: Enforces a <type>: <short description> format for PR titles from a predefined set of types (fix, feat, refactor, docs, chore, test).
Concise summaries: Provides a short, 2-5 bullet point summary for the PR body to explain what changed and why.
Automation steps: Guides steps to create PRs via the GitHub CLI (gh pr create) with a standardized body.
Use Case: When merging a small bug fix, a feature addition, or refactoring, this skill ensures PRs are consistently described for faster reviews.

Quick Start

gh pr create --title "<type>: <short description>" --body "## Summary

<what>
<why>"

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I create a standardized GitHub pull request description?▼

To create a standardized GitHub pull request description, use a predefined format combining a structured title like <type>: <short description> and a concise 2-5 bullet point summary in the PR body explaining what changed and why.

What is the best way to automate pull request creation with the GitHub CLI?▼

Automating pull request creation with the GitHub CLI involves running the gh pr create command while passing structured arguments for the title and body to ensure consistent, standardized PR generation across your development workflow.

Does the PR title format support specific commit types for GitHub reviews?▼

The PR title format supports specific commit types for GitHub reviews by enforcing a predefined set of prefixes including fix, feat, refactor, docs, chore, and test, ensuring titles clearly communicate the nature of the code changes.

Can I use this approach for both small bug fixes and larger feature additions?▼

You can use this approach for both small bug fixes and larger feature additions because it standardizes PR titles and descriptions across all merge types, ensuring consistently described changes that accelerate code review.

Why should I use standardized PR titles and summaries in my development workflow?▼

Using standardized PR titles and summaries in your development workflow reduces review time and minimizes back-and-forth communication by providing reviewers with a concise, predictable format that immediately explains what changed and why.