Create Pull Request

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

Usage

code

/create-pr

Instructions

1. Gather Context

Run these commands to understand the current state:

bash

# Get current branch name
git branch --show-current

# Check if branch needs pushing
git status -sb

# Get commits on this branch not on main
git log main..HEAD --oneline

# Get diff summary against main
git diff main...HEAD --stat

2. 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.

3. Look Up Jira Ticket

Use the /jira-ticket skill or the Jira MCP tools directly to get ticket details for the PR description:

code

mcp__jira__jira_get with:
  path: /rest/api/3/issue/{ticketNumber}
  jq: "{key: key, summary: fields.summary, description: fields.description}"

4. Generate PR Title

Use conventional commit format based on branch prefix:

Branch Prefix	PR Title Format
`feat/`	`feat(<scope>): <description>`
`fix/`	`fix(<scope>): <description>`
`refactor/`	`refactor(<scope>): <description>`
`chore/`	`chore(<scope>): <description>`
`docs/`	`docs(<scope>): <description>`
`perf/`	`perf(<scope>): <description>`

Infer the scope from changed files (e.g., offers-cms, web, api).

5. Generate PR Body

Analyze the actual code changes (use git diff main...HEAD) to write a meaningful description.

Check for a repo-specific PR template at .github/pull-request-template.md or .github/pull_request_template.md. If found, use that format. If not, ask user for confirmation on generating the body ourselves.

6. Push and Create PR

bash

# Push branch with upstream tracking
git push -u origin {branch-name}

# Create the PR targeting main
gh pr create --base main --title "{title}" --body "$(cat <<'EOF'
{body}
EOF
)"

7. Return Result

Output the PR URL so the user can view it.