pr

Create a GitHub pull request for the current branch using the repository's PR template.

Follow this exact workflow:

1. Inspect PR state:
   • Run git status --short.
   • Run git branch --show-current.
   • Run git remote -v.
   • Run git log --oneline --decorate -10.
   • Determine the base branch, preferring the repository default branch from gh repo view --json defaultBranchRef when available.
   • Run git diff <base-branch>...HEAD to understand all changes in the PR.
2. Preconditions:
   • Stop if the current branch is main or master; ask the user to create a feature branch first.
   • Stop if there are uncommitted changes; tell the user to run /zen:commit first unless they explicitly want a draft with uncommitted work excluded.
   • Ensure the branch is pushed. If not pushed, push it with the /zen:push workflow.
   • Read .github/PULL_REQUEST_TEMPLATE.md. If it is missing, stop and say the template is missing.
3. Draft the PR:

   • Use a concise title under 70 characters.

   • Fill the body according to .github/PULL_REQUEST_TEMPLATE.md.

   • Keep template headings and checklist structure intact.

   • Base the summary and test plan on the actual commits and diff, not guesswork.

   • Include this footer if the template has no conflicting footer section:

     Generated with Claude Code

4. Create the PR with GitHub CLI:
   • Use gh pr create.
   • Pass title and body via heredoc-style shell substitution to preserve formatting.
   • Do not publish sensitive data in the PR body.
5. Finish by reporting:
   • PR URL.
   • Base branch and head branch.
   • Verification/test commands included in the PR body.

Arguments from the user, if any, are additional PR instructions such as title hints, draft mode, reviewers, or labels:

$ARGUMENTS