gh-create-pr

Open a draft GitHub pull request from the current feature branch using the gh CLI.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/skaile-ai/ai-assets --skill gh-create-pr-skaile-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-create-pr
Source: https://github.com/skaile-ai/ai-assets/tree/main/github-ops/skills/gh-create-pr
Command: npx skills add https://github.com/skaile-ai/ai-assets --skill gh-create-pr-skaile-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines code reviews by automatically opening a draft pull request from the agent's feature branch, ensuring changes are review-ready.

Core Features & Use Cases

  • Open a draft PR from the current feature branch using the gh CLI.
  • Validate prerequisites (branch naming on agent/*, clean working tree, remote pushed, gh authentication) before PR creation.
  • Output the PR URL for post-processing and reporting in threads.

Quick Start

Open a draft PR for your current agent feature branch using the gh CLI.

Frequently Asked Questions about gh-create-pr

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

FAQPage Schema
How do I open a draft pull request from a feature branch using the gh CLI?

To open a draft pull request from a feature branch, the skill validates your gh CLI authentication, confirms the branch is pushed to origin, and outputs the PR URL for human review.

What prerequisites are needed to automate GitHub PR creation for code review?

Automating GitHub PR creation requires the gh CLI to be installed and authenticated, a clean working tree, and the agent feature branch to be pushed to the remote origin.

When should I use an automated draft PR for code review workflows?

Use an automated draft PR for code review workflows when your changes are on an agent feature branch and ready for CI pipelines, manual QA handoffs, or human review.

Does this GitHub PR automation work with any feature branch naming convention?

No, this PR automation is specifically applicable when changes are on an agent/* feature branch, ensuring the branch is properly named and pushed before creating the pull request.

Can I get the pull request URL after automating PR creation with the gh CLI?

Yes, after automating PR creation with the gh CLI, the skill outputs the specific pull request URL for post-processing, reporting in threads, and tracking the human review.