create-pr

Create Pull Request

Create a pull request from the current branch using project conventions.

Usage

/create-pr                              # Resolve recorded/default base
/create-pr {base-branch}                # Explicit base, including a stacked parent
/create-pr --draft {base-branch}        # Create a draft PR against that base

Instructions

Parse optional --draft plus at most one {base-branch}. Reject unknown or duplicate arguments. Expand {draft-flag} to --draft when requested and to nothing otherwise.

1. Gather context

Get the current branch and working-copy state:

git branch --show-current
git status -sb

If the branch is empty, stop: HEAD is detached. Preserve the commit on a branch before attempting to push or create a PR.

2. Resolve the PR base

Use the first available source:

1. explicit {base-branch} argument;
2. git config --get branch.{branch-name}.gh-merge-base (recorded by /stack-branch);
3. the default branch from origin/HEAD, falling back to local main, then master.

If the result is empty, equals the head branch, or does not resolve to a commit, ask rather than guessing. Fetch the selected base, then use it consistently for context and PR creation:

git fetch origin {base-branch}
git log origin/{base-branch}..HEAD --oneline
git diff origin/{base-branch}...HEAD --stat

3. Extract Jira Ticket from Branch Name

Parse the branch name to find the ticket number:

• Pattern: {type}/{TICKET-NUMBER}-{description}
• Example: feat/AB-123-sanitize-input → AB-123
• Ticket format: 2-4 uppercase letters, dash, numbers (e.g., AB-123, SSP-456)

If no ticket found, ask the user.

4. Look Up Jira Ticket

Use jira-ticket for the key, summary and description. It owns tool availability, deferred discovery and unavailable-context handoffs. If skill invocation is absent, read that installed skill and follow it; do not reconstruct the lookup. Missing context remains unavailable in the draft unless supplied by the user; never fabricate fetched requirements.