gh-pr-flow

Automate staging, committing, pushing, and creating a draft GitHub pull request with gh.

8|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill gh-pr-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-pr-flow
Source: https://github.com/ChoshimWy/iOSAgentSkills/tree/main/skills/gh-pr-flow
Command: npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill gh-pr-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates turning local changes into a review-ready PR using the gh CLI, simplifying staging, committing, pushing, and PR creation.

Core Features & Use Cases

  • Automates gh-based PR creation from the current branch by staging changes, committing with a descriptive message, pushing, and opening a draft PR.
  • Enforces a clear workflow: checks authentication, selects or creates a branch, and fills PR details via gh.

Quick Start

Ask the AI to run the gh-based end-to-end flow: stage changes, commit with a clear message, push, and create a draft PR.

Frequently Asked Questions about gh-pr-flow

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

FAQPage Schema
How do I automate creating a GitHub pull request from local changes?

Automating a GitHub pull request from local changes involves staging, committing, pushing, and opening a draft PR. This flow uses the gh CLI to enforce a clear workflow, ensuring proper authentication checks and branch handling before creating a review-ready PR.

What is the best way to create a draft PR with the GitHub CLI?

Creating a draft PR with the GitHub CLI is done by pushing committed local changes and running the gh pr create command with the draft flag. This workflow fills PR details directly from the current branch to prepare it for team review.

How does a gh-based end-to-end PR flow handle branch creation?

A gh-based end-to-end PR flow handles branch creation by selecting an existing branch or creating a new one before staging changes. It ensures local commits are pushed to the correct remote branch before opening a draft PR.

Do I need to check GitHub authentication before pushing commits and creating a PR?

You need to check GitHub authentication before pushing commits to ensure the gh CLI can access your repository. The automated PR flow enforces this check prior to branch handling and draft PR creation to prevent remote permission errors.

Can I stage, commit, and push local git changes in one automated workflow?

You can stage, commit, and push local git changes in one automated workflow by running a gh-based end-to-end flow. It sequentially stages files, commits with a descriptive message, and pushes to GitHub before creating a draft PR.

When should I use an automated PR creation workflow instead of manual git commands?

You should use an automated PR creation workflow when you need a review-ready GitHub pull request without manually running individual git commands. It enforces a clear process for staging, committing, pushing, and opening a draft PR from the current branch.