Gh Pr

Create a GitHub pull request from the current branch using gh with a title and body derived from the branch diff. Support draft vs in-review (ready) state, and switch state for an existing PR when requested.

Workflow

1. Inspect repo state. Run git status --short --branch to confirm current branch and working tree state. If the repo has uncommitted changes that should be included, confirm with the user whether to proceed or wait for commits.

2. Determine base branch. If the user specifies a base, use it. Otherwise check git config --get branch.$(git rev-parse --abbrev-ref HEAD).gh-merge-base. If unset, use gh repo view --json defaultBranchRef -q .defaultBranchRef.name to get the default branch. If the base branch is missing locally, run git fetch origin <base>.

3. Build PR title and description from the diff. Use git diff --stat <base>...HEAD to summarize changes. Use git diff <base>...HEAD (or --stat plus file-level highlights) to describe the diff in prose. Keep the title concise (about 50–72 chars) and focused on what changed. The description should include a short summary and a bullet list of key file-level changes.