PR Create

Create a pull request from local changes with consistent, low-friction steps.

Workflow

1. Confirm Current State

• Check current branch and working tree status.
• If there are no changes and no new commits to publish, report and stop.

2. Branch Strategy

• If user requests a new branch, create and switch to it from the current branch.
• If user says to continue on current branch, keep it.

3. Commit Changes

• Review changed files quickly for scope sanity.
• Stage only relevant files.
• Write a clear Conventional Commit-style message when possible.
• Commit.

4. Push Branch

• If you created a new branch in step 2, push with upstream tracking:
  • git push -u origin <branch-name>
• If you are continuing on the current branch, push current HEAD:
  • git push
  • or git push origin HEAD (explicit form)

5. Open PR

• Create PR with gh pr create.
• Use explicit --base and --head when known.
• Include concise summary and verification notes in PR body.
• After PR creation, open it in the browser with gh pr view --web.

6. Report Back

• Return branch name, commit hash, and PR URL.
• Mention anything skipped (for example, tests not run).

Safety Checks

• Do not include unrelated files in commit.
• Do not use destructive git commands unless explicitly requested.
• If branch name, base branch, or PR title is ambiguous, ask the user.

Minimal Command Sequence

git status --short
git rev-parse --abbrev-ref HEAD
git checkout -b <branch-name>   # only when requested
git add <files...>
git commit -m "<message>"
# if new branch was created
git push -u origin <branch-name>
# if continuing on current branch
git push
# or explicit
git push origin HEAD
gh pr create --base <base> --head <branch-name> --title "<title>" --body "<summary>"
gh pr view --web