pr

Gather Context

1. git branch --show-current

   — check current branch

2. git remote show origin 2>/dev/null | grep 'HEAD branch' | awk '{print $NF}' || echo main

   — detect default branch

3. git log --oneline main..HEAD 2>/dev/null || git log --oneline -10

   — list commits on this branch

4. git diff main...HEAD --stat 2>/dev/null || echo "Could not determine diff"

   — list changed files

5. gh pr list --state merged --limit 5 --json number,title,headRefName --jq '.[] | "#\(.number) \(.title) (\(.headRefName))"' 2>/dev/null || echo "Could not fetch PR history"

   — reference recent PR title style

Determine PR Type

$ARGUMENTS

• If it contains "release" → use the Release PR Template below.
• Otherwise → use the Individual PR Template.

PR Title Convention

{Type}: {description}

Type Prefixes (capitalize first letter — differs from commit messages)

Feat:

Fix:

Refactor:

Perf:

Docs:

Test:

Chore:

Hotfix:

Release:

Release: dev → main 통합 (v0.5.0)

Individual PR Template

## 📌 개요

{1-3 sentences: background, problem, and solution}

> ⚠️ **Breaking Change**: {only if applicable — describe migration needed}

## ✅ 변경 사항

### 1. {Change category title}

{Detailed description. Include before/after comparisons, code snippets, or diagrams where helpful.}

### 2. {Change category title}

{...}

## 📁 파일 변경 요약

| 구분 | 파일 |
|------|------|
| 추가 | `path/to/new/file.py` |
| 수정 | `path/to/modified/file.py` |
| 삭제 | `path/to/deleted/file.py` |

## 🧪 테스트

- [ ] {Test item 1}
- [ ] {Test item 2}

## 📌 관련 이슈/PR

- #{number}

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Release PR Template

$ARGUMENTS

dev → main

gh pr list --state merged --base dev --limit 30 --json number,title --jq '.[] | "- #\(.number) \(.title)"'

Release: dev → main 통합 (vX.Y.Z)

## 📝 개요

{Release summary — what this release includes}

> ⚠️ **배포 공지**: {Deployment impact notice — which servers are affected, migration steps if any}

## ✨ 주요 변경사항

### 1. {Feature/Fix name} (#{PR number})

{Brief summary of this PR's changes}

### 2. {Feature/Fix name} (#{PR number})

{...}

## 📁 변경된 파일

| 파일 | 변경 내용 |
|------|----------|
| `file.py` | {description} |

## 🔍 테스트

- [ ] {Test checklist item}

## 📌 관련 PR

- #{number1}
- #{number2}

## 🚀 배포 정보

| 환경 | 서버 | 브랜치 |
|------|------|--------|
| 개발 | {dev server} | dev |
| 운영 | {prod server} | main |

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Task

1. Analyze all commits on the current branch (vs. base branch) to understand the full scope.
2. Determine PR type: Release (if

   $ARGUMENTS

   contains "release") or Individual.
3. Draft the PR title and body using the appropriate template above.
4. Present the proposed title and body to the user and wait for approval.
5. Once approved:
   • Push the branch if not already pushed:

     git push -u origin {branch-name}

   • Create the PR:

     gh pr create --title "..." --body "$(cat <<'EOF' ... EOF)"

6. Return the PR URL.

• Do NOT push or create a PR without explicit user approval.
• For Release PRs, automatically collect all included PRs from the merge history.
• Adapt section headers and content language to the project's CLAUDE.md language setting.
• The file change table should be generated from the actual diff, not guessed.