write-pr

name	write-pr
description	Generate PR title, body, and labels from commits since the base branch, then create the PR on GitHub. Handles base branch detection, label selection, and PR creation end-to-end.

Step 1 — Gather Context

git branch --show-current
git log origin/develop..HEAD --oneline 2>/dev/null || git log --oneline -15
git diff origin/develop...HEAD --stat 2>/dev/null || git diff HEAD~5...HEAD --stat
git diff origin/develop...HEAD 2>/dev/null || git diff HEAD~5...HEAD

Also read the PR template:

cat .github/PULL_REQUEST_TEMPLATE.md

Step 2 — Determine Labels

Read references/labels.md and select 1–2 appropriate labels based on the nature of the changes.

Step 3 — Generate PR Content

Title — Generate 3 options in the format [scope] description:

• Scope: Module name ([user], [authorization], [gateway], [chat], etc.) or [global] / [ci/cd] for cross-cutting changes
• Description: Korean, concise, no emojis, max 50 characters total
• Mark the best option with ← 추천

Body — Follow the .github/PULL_REQUEST_TEMPLATE.md structure:

• Korean 합쇼체: ~하였습니다, ~되었습니다, ~추가하였습니다
• No emojis
• Max 2500 characters

Step 4 — Write Body & Show Preview

Write the body to PR_BODY.md, then display:

## 추천 PR 제목
1. [title1]
2. [title2]
3. [title3] ← 추천

## 선택된 라벨
- label1, label2

## PR 본문 미리보기
[body content]

Ask the user to confirm which title to use. If no answer is given, proceed with the recommended (marked) title.

Step 5 — Create PR

Run the creation script with the confirmed title and labels:

bash .agents/skills/write-pr/scripts/create-pr.sh "<confirmed-title>" "PR_BODY.md" "<label1>,<label2>"

After creation, display the PR URL.

Step 6 — Cleanup

rm -f PR_BODY.md