gh-pr-create

Create GitHub pull requests with standardized bodies using gh pr create.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/saadjs/agent-skills --skill gh-pr-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-pr-create
Source: https://github.com/saadjs/agent-skills/tree/main/skills/gh-pr-create
Command: npx skills add https://github.com/saadjs/agent-skills --skill gh-pr-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate and publish a GitHub Pull Request from a clean working tree, eliminating manual PR drafting and submission steps.

Core Features & Use Cases

  • Auto-detects a clean working tree and a suitable feature branch for PR creation.
  • Generates a standardized PR body with sections like Summary and Major changes, plus optional Screenshots, Tests, and Additional info.
  • Uses gh pr create to open the PR on GitHub with an appropriate base branch and title.

Quick Start

Push your commits to a feature branch, then run the gh-pr-create skill to open a PR with a standardized body.

Frequently Asked Questions about gh-pr-create

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

FAQPage Schema
How do I automatically create a GitHub pull request from the command line?▼

Automatically create a GitHub pull request by running a skill that checks for a clean working tree, determines the base branch, generates a standardized PR body, and executes gh pr create to publish the PR.

What is the best way to structure a PR body for GitHub pull requests?▼

A structured GitHub pull request body should include a Summary and Major changes section, supplemented by optional Screenshots, Tests, and Additional info sections to provide comprehensive context for reviewers.

Do I need a clean working tree before creating a pull request with gh CLI?▼

Yes, a clean working tree with incremental commits committed and pushed to a feature branch is required before automatically opening a GitHub pull request using the gh CLI.

How does a feature branch determine the base branch for a pull request?▼

When creating a pull request from a feature branch, the base branch is correctly determined automatically to ensure the GitHub PR targets the appropriate integration branch without manual configuration.

Can I include screenshots and test details in an automated GitHub PR body?▼

Yes, the automated GitHub PR body generation supports optional Screenshots and Tests sections, allowing you to include visual proofs and testing context alongside the Summary and Major changes.

What should I do if my working tree is not clean before automating a pull request?▼

If your working tree is not clean, you must commit or stash incremental changes and push them to your feature branch before attempting to automate GitHub pull request creation.