imvanzen/create-pull-request

Create Pull Request

When to apply

• User requests creating a pull request, "open a PR", "create a PR", submit changes for review, or branch is ready for review.

Procedure

Step 1: Extract required information from context

Before asking the user, extract from available context:

| Field | Source | Fallback | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | | Ticket number | Branch name (PAIC-123, TW-456), commit messages, file changes | Ask: "What is the ticket number (e.g. PAIC-123)?" | | Commit type | Changes: new features → feat, bug fixes → fix, docs → docs, refactor → refactor, tests → test, config → chore | Ask: "What type? (feat/fix/docs/refactor/test/chore)" | | Scope | Modified paths: apps/backend/** → backend, apps/checkout/** → checkout, apps/dashboard/** → dashboard | Omit if multiple/unknown | | Short description | Primary change, present tense, lowercase, no period | Ask if unclear | | Labels | feat → enhancement, fix → bug, docs → documentation | Only from: bug, documentation, duplicate, enhancement, good first issue, help wanted, invalid, question, wontfix | | Analysis of changes | Git diff / file changes → bullet points (user-visible or significant) | Ask: "What changes does this PR include?" |

Step 2: Locate and read PR template

Use GitHub MCP to read the PR template. Try in order:

• .github/pull_request_template.md
• pull_request_template.md
• PULL_REQUEST_TEMPLATE.md
• .github/PULL_REQUEST_TEMPLATE/pull_request_template.md

If found: preserve all sections, placeholders, and formatting. If not found, use:

# Issue: [TICKET-NUMBER](link-if-available)

## Description

[Analysis of Changes]

Step 3: Construct PR title

Format: type(scope): ticket-number description or type(scope): description if no ticket.

• With scope: feat(backend): PAIC-123 add user authentication
• No scope: fix: PAIC-456 resolve payment timeout
• Lowercase, no period, under 72 characters when possible, max 100.

Step 4: Construct PR body

1. Start with template from Step 2.
2. Replace: [PAIC-xxx] / [TICKET-NUMBER] → actual ticket; [PAIC-xxx](https://masterborn.atlassian.net/browse/PAIC-xxx) → real link; Description → Analysis of Changes (bullets).
3. Preserve all other sections, checklists, HTML comments (<!--- ... -->). Do not remove template structure.

Step 5: Get branch and repo info

1. Current branch: git branch --show-current
2. Authenticated user: GitHub MCP get-me
3. Repository owner/name from git remote or workspace

Step 6: Create pull request

Call GitHub MCP create-pull-request with:

• title: Step 3
• body: Step 4 (full filled template)
• head: current branch
• base: default branch (main / master)
• draft: false unless user asks for draft
• labels: from Step 1 (max 10)
• assignees: [authenticated user's username]

Decision rules

Ticket priority: Branch name → commit messages → modified files → ask user.

Commit type: New business logic → feat; fix incorrect behavior → fix; docs only → docs; restructure no behavior change → refactor; tests only → test; config/build → chore. If multiple, use most significant.

Scope: 80%+ changes in one app dir → that scope; multiple apps or root → omit.

Labels: feat → enhancement, fix → bug, docs → documentation; others no auto-label unless user specified.

Constraints

• Title ≤ 100 chars. Body preserves template exactly.
• Do not create PR if current branch is default or there are no commits ahead of base.
• Do not create if git status has uncommitted changes (warn user first).
• Do not modify template structure; do not remove sections; do not guess ticket (ask if uncertain).
• Allowed labels only; max 10 labels.

Non-goals: PR reviews, updating existing PRs, branch protection, running CI.

Validation before create

• [ ] Title is conventional format
• [ ] Body has no unfilled [PAIC-xxx] placeholders
• [ ] Ticket format valid (if provided)
• [ ] Current branch ≠ default branch
• [ ] Labels from allowed list
• [ ] Assignee = current user

Error handling

Missing info: If no ticket and user doesn’t give one → proceed with type(scope): description. If type ambiguous → ask user to choose.

Template: If unreadable → use minimal template. If odd format → keep structure, fill obvious placeholders.

Git: Uncommitted changes → warn and ask to commit first. Branch behind base → inform but can proceed. Branch not on remote → user must push first.

GitHub API: Repo not found → check name and permissions. Invalid labels → create PR without those, inform user. Invalid assignee → create without assignee, inform user.

On success: confirm PR number and URL, show title and key details, confirm labels and assignee.