create-github-pr

Automate GitHub pull request creation with the gh CLI.

Updated Apr 20, 2026
One-click install
npx skills add https://github.com/x402agent/openclawd-stack --skill create-github-pr-x402agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-github-pr
Source: https://github.com/x402agent/openclawd-stack/tree/main/openclawd-stack/OpenShell-main/.agents/skills/create-github-pr
Command: npx skills add https://github.com/x402agent/openclawd-stack --skill create-github-pr-x402agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation of GitHub pull requests by automating PR creation and standardizing metadata, reducing manual steps and errors.

Core Features & Use Cases

  • Create PRs on GitHub using the gh CLI with a consistent title and body.
  • Validate that the working branch is pushed and authenticated before PR creation.
  • Use in team workflows to quickly open PRs for code review, issue linking, and collaboration across repositories.

Quick Start

Run gh pr create to open a PR with a descriptive title and body.

Frequently Asked Questions about create-github-pr

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

FAQPage Schema
How do I automate GitHub pull request creation using the gh CLI?

GitHub pull request creation is automated using the gh CLI by validating branch naming and enforcing consistent PR title and description formatting for code review workflows. The skill streamlines opening PRs across repositories by applying standardized metadata to reduce manual steps and errors.

Do I need to authenticate the gh CLI before creating a pull request?

Yes, gh authentication is required before creating a pull request using the gh CLI. The skill validates that the working branch is pushed and authenticated prior to PR creation to ensure consistent title and body formatting across repositories without manual intervention.

What's the best way to standardize PR titles and descriptions for code review?

The best way to standardize PR titles and descriptions for code review is to enforce formatting rules during pull request creation via the gh CLI. This approach validates branch naming and applies consistent metadata to reduce errors and streamline team collaboration across repositories.

Why does branch validation fail when I try to open a GitHub PR?

Branch validation fails when opening a GitHub PR if the working branch is not pushed to the remote repository or if the gh CLI is not properly authenticated. Ensure local commits are pushed and gh authentication is active before attempting automated pull request creation.

Can I link issues to a pull request automatically with the gh CLI?

Yes, you can link issues to a pull request automatically within team workflows using the gh CLI. The skill automates PR creation and standardizes metadata to facilitate issue linking and collaboration across repositories for code review purposes.