gh-pr

name	gh-pr
description	Create Pull Request with structured description. Use when creating PR, opening pull request. Triggers on "/gh-pr", "create pr", "建立 PR", "開 PR".
allowed-tools	Bash, Read, Glob, Grep
version	1.0.0
scope	public
evolution	{"enabled":true,"version":"1.0.0","stability":"stable","auto_evolve":"patch","created":"2026-01-18T00:00:00.000Z","updated":"2026-01-18T00:00:00.000Z","history":[]}

GH PR - Create Pull Request

Automatically analyze changes on the current branch, generate a structured PR description, and create a Pull Request.

Methodology:

• GitHub Flow - Clear PR workflow
• Conventional Commits - Structured descriptions

---

Integrations

upstream:
  - skill: gh-commit-and-push
    receives: Pushed branch changes
  - skill: auto-cycle (COMMIT phase)
    receives: Completed development tasks

downstream:
  - output: GitHub Pull Request
    produces: Reviewable PR

---

Out of Scope

• Merging PRs - Only creates, does not merge
• Resolving conflicts - Requires manual handling
• Modifying existing PRs - Only creates new PRs
• Cross-repo PRs - Only handles same-repo PRs

---

When to Use

Use cases:

• Feature development complete, need to create a PR
• Already pushed to feature branch, need review
• After auto-cycle completes, need to create PR

Not suitable for:

• Haven't committed / pushed yet
• Need to rebase / squash
• Need to merge or close PR

---

Workflow

Phase 1: Check Status

1. Confirm current branch

   git branch --show-current
   

   • If on main/master, warn and stop
   • Confirm branch has been pushed to remote

2. Check remote status

   git fetch origin
   git status -sb
   

   • Confirm local and remote are in sync
   • If there are unpushed commits, prompt to push first

3. Check if PR already exists

   gh pr list --head $(git branch --show-current)
   

   • If PR already exists, show link and ask if they want to update the description

Phase 2: Analyze Changes

4. Get diff statistics

   # Find base branch (main or master)
   BASE_BRANCH=$(git remote show origin | grep 'HEAD branch' | cut -d: -f2 | xargs)
   
   # Get diff
   git diff ${BASE_BRANCH}...HEAD --stat
   git log ${BASE_BRANCH}...HEAD --oneline
   

5. Classify changes

   Determine PR type based on files and commit messages:

   Indicator	PR Type
   Commits contain feat:	feature
   Commits contain fix:	bugfix
   Commits contain docs:	documentation
   Commits contain refactor:	refactor
   Mixed types	Use the most prominent type

Phase 3: Generate PR Description

6. Generate title

   Format: [type] short description

   Examples:

   • [feat] Add user login feature
   • [fix] Fix API timeout issue
   • [refactor] Restructure database connection pool

7. Generate content

   ## Summary
   
   - Change 1
   - Change 2
   - Change 3
   
   ## Changes
   
   | File | Change |
   |------|------|
   | src/auth/login.ts | Add login logic |
   | src/app.ts | Register auth routes |
   
   ## Test Plan
   
   - [ ] Unit tests pass
   - [ ] Manually test XXX feature
   - [ ] Confirm XXX scenario
   
   ---
   
   Generated with Claude Code
   

Phase 4: Create PR

8. Run gh pr create

   gh pr create \
     --title "[type] title" \
     --body "$(cat <<'EOF'
   ## Summary
   ...
   EOF
   )" \
     --base main
   

9. Display results and suggest reviewers

   • Show PR URL
   • Check for CODEOWNERS:

     # Look for CODEOWNERS in standard locations
     cat CODEOWNERS 2>/dev/null || cat .github/CODEOWNERS 2>/dev/null || cat docs/CODEOWNERS 2>/dev/null
     

   • If CODEOWNERS exists, match changed file paths against entries and display relevant code owners as suggested reviewers
   • If no CODEOWNERS, skip reviewer suggestion silently

---

Implementation Checklist

Pre-execution checks:

• Current branch is not main/master
• All changes have been committed and pushed
• No unresolved merge conflicts

Analysis phase:

• Get diff from base branch
• Analyze commit history
• Determine PR type

Generate PR:

• Title is concise and clear (<=72 characters)
• Summary lists main changes
• Has Test Plan section
• Run gh pr create

Completion confirmation:

• PR created successfully
• Display PR URL

---

Verification

Success Criteria

PR Description Quality:

• Title includes type label [feat]/[fix]/[docs]
• Summary clearly lists key changes
• Has Test Plan section
• Appropriate length, not overly verbose

Git Operation Success:

• gh pr create executed successfully
• PR link is accessible
• PR points to the correct base branch

Verification Commands

# Confirm PR has been created
gh pr list --author @me

# View PR details
gh pr view

# Open in browser
gh pr view --web

---

Safety and Escalation

Situations to Stop Execution

Situation	Reason	Action
On main/master branch	Should not create PR from main	Prompt to create a feature branch first
Unpushed commits exist	Remote doesn't have latest code	Prompt to push first
PR already exists	Avoid duplicate creation	Show existing PR link
gh not logged in	Cannot operate	Prompt to run gh auth login
No network connection	Cannot reach GitHub	Display error

---

PR Template Reference

Feature PR

## Summary

Add [feature name], implementing [goal].

- Implement XXX
- Support YYY
- Integrate ZZZ

## Changes

| File | Change |
|------|------|
| `src/feature.ts` | Add feature implementation |
| `src/feature.test.ts` | Add tests |

## Test Plan

- [ ] Unit tests pass (`npm test`)
- [ ] Manually test feature A
- [ ] Confirm edge case B

---

Generated with Claude Code

Bugfix PR

## Summary

Fix [problem description].

**Root cause**: [explain root cause]
**Solution**: [explain fix method]

## Changes

| File | Change |
|------|------|
| `src/utils.ts` | Fix XXX logic |

## Test Plan

- [ ] Original issue no longer occurs
- [ ] Related tests pass
- [ ] No regressions

---

Generated with Claude Code

---

Example Usage

Example 1: Feature PR

# On feature/user-auth branch
/gh-pr

# Output:
# PR created successfully
# https://github.com/owner/repo/pull/123
#
# [feat] Add user authentication module
#
# Summary:
# - Implement email + password login
# - Support JWT tokens
# - Add auth middleware

Example 2: PR Already Exists

/gh-pr

# Output:
# PR #123 already exists
# https://github.com/owner/repo/pull/123
#
# Update PR description? [y/N]

---

Quick Start

# Run on a feature branch
/gh-pr

# The skill will automatically:
# 1. Check branch status
# 2. Analyze changes
# 3. Generate PR description
# 4. Create PR
# 5. Display PR URL