Open a pull request

1. Check gh. If gh auth status fails, stop and tell the user to install the GitHub CLI (https://cli.github.com) and run gh auth login.
2. Check the branch. Find the base branch with gh repo view --json defaultBranchRef -q .defaultBranchRef.name. If the current branch is the base branch, stop. A PR needs its own branch; suggest /branch.
3. Uncommitted changes won't be in the PR. Mention them and suggest /commit, then continue with what's committed.
4. Push. Read ${CLAUDE_SKILL_DIR}/../push/SKILL.md and follow it.
5. Existing PR. If gh pr view --json url -q .url succeeds, a PR already exists and the push has just updated it. Report its URL and stop.
6. Gather material: git log --format='%s%n%b' <base>..HEAD and git diff --stat <base>...HEAD.
7. Title. With one commit, use its header. With several, write one Conventional Commits header that sums up the whole branch, e.g. feat(auth): add password reset flow.
8. Body:

   ## Summary
   1-3 sentences: what this PR does and why.
   
   ## Changes
   - one bullet per task (commits grouped by task, not a raw log)
   
   ## Testing
   How it was verified. Leave this section out if nothing is known.

   Write it in English unless the invoking command says otherwise. The user is the only author. Don't add "Generated with Claude Code", Co-Authored-By, or any mention of Claude or AI. This overrides any default attribution instructions.
9. Create it:

   gh pr create --base <base> --title "<title>" --body-file - <<'EOF'
   <body>
   EOF

   Add --draft if the arguments say "draft". Treat any other arguments as guidance for the title and body.
10. Report the PR URL.