create-github-pr

Create GitHub PR

Structured workflow for creating high-quality GitHub pull requests with proper context, testing steps, and user approval.

When to Use

• Creating a new pull request
• Asked to "open a PR" or "submit for review"
• Branch is ready to merge

PR Template

FIRST: Check for .github/PULL_REQUEST_TEMPLATE.md

• If template exists: use it, fill all sections, complete checklist
• If NO template: use description template from Phase 2 below
• Template sections override generic guidelines

PR Creation Workflow

Phase 0 — Pre-flight Checks

HALT if any fail:

1. git branch --show-current - Must NOT be on trunk (or default branch)
2. git status - No uncommitted changes
3. Identify <base_branch>:
   • Run: git log --oneline --decorate --all --graph -20 to visualize branch structure
   • Run: git merge-base --fork-point <likely_base> HEAD to find fork point
   • The base branch is typically where the current branch was created from (may differ from repo default)
4. git log <base_branch>..HEAD - Has commits to include
5. git fetch && git status - Up to date with remote
6. Check for existing PR:

   gh pr view --json url,state 2>/dev/null || echo "NO_EXISTING_PR"
   

   • If a PR already exists, show the URL and state. Ask user whether to update the existing PR or create a new one. HALT until answered.

Phase 1 — Gather Context

Run in parallel:

• git log --oneline <base_branch>..HEAD - List commits
• git diff <base_branch>...HEAD - Code changes
• git rev-parse --abbrev-ref HEAD - Branch name

Phase 2 — Generate PR Content

Issue Detection from Branch Name:

• Linear issue: feature/PROJ-123-desc → Closes PROJ-123
• GitHub issue: fix/issue-123-bug → Closes #123
• Common patterns: WOOPLUG-123, WOOPMNT-456, TRAPLAT-789, DEVELOPER-321

Wrap analysis in <pr_analysis> tags:

<pr_analysis>
- Branch name: What issue/feature does it reference?
- Issue number: Extract from branch (Linear ID or GitHub #number)
- Commits: List significant ones (skip style/misc fixes)
- Code changes: What functionality changed?
- Testing: What coverage exists? What manual testing needed?
</pr_analysis>