create-pr

Create PR for an octomux task

Create a GitHub pull request directly using gh pr create. The octomux dashboard will auto-detect the PR within 30 seconds.

Steps

1. Identify the task branch and repo:

   • Ask the user which task, or infer from context
   • Get the task details (branch, repo_path, worktree):

     octomux get-task <task-id>
     

   • You need branch, repo_path, and base_branch. The task's base_branch is the PR base branch. If not set, default to main.

2. Gather context for the PR description:

   Use the task's base_branch as <base>:

   git -C <worktree> log <base_branch>..HEAD --oneline
   git -C <worktree> diff <base_branch>...HEAD --stat
   

3. Check if branch is pushed and push if needed:

   # Check if remote tracking branch exists
   git -C <repo_path> ls-remote --heads origin <branch>
   

   If the branch is not pushed yet, push it:

   git -C <repo_path> push -u origin <branch>
   

   If already pushed, check if local is ahead and push any new commits:

   git -C <worktree> status -sb  # check if ahead of remote
   git -C <repo_path> push origin <branch>  # push if ahead
   

4. Draft the PR title and body, then confirm with the user:

   Title: Conventional commit format, under 70 chars, min 10 char description:

   <type>(<scope>): <description>
   

   Types: feat, fix, chore, refactor, docs, test, perf Examples: feat(hooks): add permission prompt tracking, fix(terminal): clean up orphaned tmux sessions

   Body: Must include all three sections — What, Why, and Testing:

   ## What
   
   <Description of what this PR does — summarize the changes>
   
   ## Why
   
   <Explanation of why this change is needed — the motivation>
   
   Resolves <link>
   
   ## Testing
   
   <How this was tested — commands run, manual verification, etc.>
   

   Linking tickets/issues:

   • If the task was created from a Jira ticket, include the Jira link
   • If the task was created from a GitHub issue, include: Resolves #<issue-number>
   • Infer the ticket/issue from the branch name. Jira-style keys match [A-Z][A-Z0-9]+-\d+ (e.g., feat/PROJ-123-... -> PROJ-123); numeric branches resolve to GitHub issues (fix/42-... -> #42).
   • If no ticket/issue is associated, omit the Resolves line