create-pull-request（创建拉取请求）

Create Pull Request

Mode: $ARGUMENTS

If --draft is passed, create as draft PR.

Pre-loaded context

• Branch status:!git status && git branch -vv
• Recent commits:!git log --oneline -10

Workflow

1. Run in parallel:

- git fetch origin && git remote show origin | grep 'HEAD branch' | cut -d' ' -f5 (get base branch) - git rev-parse --abbrev-ref HEAD | grep -oE '[A-Z]+-[0-9]+' (extract ticket ID) - Search for PR template (see template-locations.md)

1. Run in parallel:

- git diff HEAD - git diff [base-branch]...HEAD --unified=0

1. Read template if found
2. Review ALL commits (not just latest)
3. Ask the user (use AskUserQuestion when available; otherwise ask directly). Ask all at once where possible:

- Effort (required): how long the task took in hours (planning, reading, testing, all included) - Changes (required): general overview of what was done - Testing (optional): testing done that isn't visible in the diff - Tricky parts (optional): anything hard, requiring multiple attempts, or non-obvious - If template found, also surface any template-specific fields that can't be inferred from the diff (e.g. "Does this include breaking changes?", "What type of change is this?")

1. Draft title and body:

- Title must match: /^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\(.*\))?:.+$/ - If template found: use the template verbatim as the body base — fill every section/placeholder using diff + user answers; check applicable checkboxes; do NOT add sections not in the template; do NOT omit any template sections - If no template: use Summary + Test plan - Reference ticket ID in body if found (e.g. Resolves TICKET-123) - Incorporate user's answers into description — don't just repeat the diff

1. In parallel:

- Create branch if needed - Push with -u if needed - Create PR with gh pr create using HEREDOC (add --draft if requested)

See examples.md for output format and gh-flags.md for advanced options.

Rules

• If a PR template exists, the body MUST be the filled template — not a summary that references it
• Analyze ALL commits, not just the latest
• Return PR URL when done
• Use gh CLI only
• NEVER force push to main/master
• NEVER push without user confirmation if already on main/master
• NEVER create PR with uncommitted changes — commit first

Error Handling

• If gh pr create fails with "already exists" → run gh pr view and return existing PR URL
• If branch is not pushed → run git push -u origin HEAD before creating PR
• If gh auth status fails → ask user to run gh auth login and retry