create-pr

Create PR — Pull Request Creation Workflow

This skill creates a pull request for the current branch: syncs with main, builds, generates Rush change files if needed, captures screenshots for visual changes, and opens the PR with proper issue linking.

Step 0: Detect Context

Determine the issue number using this priority:

1. If an argument was provided, use it as ISSUE_NUMBER
2. Otherwise, extract from the branch name (pattern: <user>/<issue>-<feature>, e.g., nick-pape/149-agent-subtask-creation → ISSUE_NUMBER=149)
3. If neither yields a number, set ISSUE_NUMBER="" (no issue linked — the PR will be created without a Closes reference)

Set variables for subsequent steps:

OWNER=$(gh repo view --json owner --jq '.owner.login')
REPO=$(gh repo view --json name --jq '.name')
BRANCH=$(git branch --show-current)

If ISSUE_NUMBER is set, fetch the issue title for use in the PR title:

gh issue view $ISSUE_NUMBER --json title --jq '.title'

Step 1: Verify Branch State

1. Ensure not on main — if on main, tell the user to create a feature branch and stop
2. Check for uncommitted changes (git status --porcelain) — if any, ask the user whether to commit or stash them
3. Check for unpushed commits (git log @{u}..HEAD or if no upstream, note that push is needed)
4. Check if a PR already exists for this branch:

   gh pr view --json number,url 2>/dev/null
   

   If a PR already exists, report its URL and stop. Suggest using /pr-fixup instead.

Step 2: Sync with Main

git fetch origin
git merge origin/main

If merge conflicts arise:

1. List conflicted files with git diff --name-only --diff-filter=U
2. Read each conflicted file and resolve the conflicts intelligently
3. Stage the resolved files and commit the merge

Step 3: Build Verification

rush build

If the build fails, fix the errors, commit the fixes, and re-run. Only proceed once the build succeeds.

Step 4: Generate Change Files (if needed)