create-pr

Create GitHub pull requests with templates and branch naming checks.

1|1|Updated Jan 6, 2026

Search Tags:#github #code-review #pull-request #branch-naming #gh-cli #pr-description

Ready to run

npx skills add https://github.com/sontek/agent-skills --skill create-pr-sontek

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Create PR skill helps engineers craft concise, effective pull requests that are easy to review, describe why changes were made, and avoid unnecessary noise.

Core Features & Use Cases

PR templating and guidance: ensure descriptions follow a consistent structure and voice.
Branch naming and checks: recommend or enforce conventional branch names like feature/ or fix/ with clear scope.
Self-review prompts: guide the author to verify changes, review diffs, and ensure no secrets or debugging code remain.
When used with GitHub CLI, it can draft descriptions, verify PR templates, and prepare a ready-to-create PR with a clean message.

Quick Start

Quick Start: Run gh pr create --fill from your current branch to auto-populate a concise PR description following the guidance.

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 review-ready pull request with a clean description using GitHub CLI?▼

To create a review-ready pull request, run gh pr create --fill from your current branch. This auto-populates a concise PR description by checking for repository templates, verifying branch state, and enforcing branch naming conventions to ensure clean changes.

What's the best way to enforce conventional branch naming like feature/ or fix/ before opening a PR?▼

The best way to enforce conventional branch naming is to use a PR creation workflow that verifies branch state and recommends clear scopes like feature/ or fix/ before composing the pull request description, ensuring branches align with team conventions automatically.

How does PR templating work with gh CLI to keep descriptions aligned with team conventions?▼

PR templating works by checking the repository for existing pull request templates, then using the gh CLI to draft descriptions that follow that consistent structure and voice, ensuring changes are prepared with a clean, review-ready message.

Can I automate self-review prompts to check for secrets or debugging code before creating a PR?▼

Yes, you can automate self-review prompts during PR creation. The workflow guides the author to verify diffs, review changes, and ensure no secrets or debugging code remain before composing the final description and opening the pull request.

Do I need GitHub CLI installed to draft PR descriptions and verify templates across repositories?▼

Yes, you need the GitHub CLI (gh) installed. The PR creation workflow relies on the gh CLI to verify templates, verify branch state, draft descriptions, and prepare the ready-to-create pull request across GitHub repositories.

Why does my pull request description lack a consistent structure when opening PRs across multiple GitHub repositories?▼

Your pull request description lacks a consistent structure because it is not applying repository PR templates. By checking for templates and enforcing PR template usage during creation, descriptions follow a consistent structure and voice across multiple repositories.