gh-pr

Create Pull Request

Create a pull request with full code review, quality gates, and reviewer suggestions.

Tool Usage: This workflow uses the AskUserQuestion tool for interactive decisions.

Phase 1: Pre-flight

1. Verify current branch:

   BRANCH=$(git branch --show-current)
   # Ensure not on main
   

2. Check for uncommitted changes:

   git status --porcelain
   

   If changes exist, use AskUserQuestion:

   • Option 1: "Run /gh-commit first" (Recommended)
   • Option 2: "Continue without committing"

3. Extract issue from branch:

   ISSUE_NUM=$(echo $BRANCH | grep -oE 'issue-[0-9]+' | grep -oE '[0-9]+')
   gh issue view $ISSUE_NUM --json title,body
   

Phase 2: Code Review

Run systematic code review on the diff:

git diff main..HEAD

Review Checklist:

• Logic correctness and edge cases
• Security (no hardcoded secrets)
• No TODO/FIXME comments
• No debug statements (console.log)
• Type safety

Categorize findings:

• P1 (Critical): Blocks PR
• P2 (Important): Should fix
• P3 (Suggestions): Nice to have

If P1 issues found, use AskUserQuestion:

• Option 1: "Fix issues now" (Recommended)
• Option 2: "Proceed anyway"

Phase 3: Quality Checks

# Run plugin validation
ls plugins/*/.claude-plugin/plugin.json
cat plugins/*/.claude-plugin/plugin.json

Phase 4: Reviewer Suggestion

1. Get collaborators:

   REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
   gh api repos/$REPO/collaborators --jq '.[] | select(.permissions.push) | .login'
   

2. Get file contributors:

   CHANGED_FILES=$(git diff --name-only main..HEAD)
   git log --format='%an' --since="30 days ago" -- $CHANGED_FILES | sort | uniq -c | sort -rn
   

3. Present suggestions with AskUserQuestion:

   • Option 1: "@{top_contributor}" (Recommended)
   • Option 2: "@{other_contributor}"
   • Option 3: "No reviewer"