/pr-merge - Merge Pull Request

PR 머지 전 검증과 머지 전략을 일관되게 수행합니다.

Cost Optimization Strategy

This skill uses Haiku subagent for all operations (~70% cost reduction).

• Main session (Sonnet/Opus): User interaction only
• Haiku subagent: Bash PR merge operations

Input

• pr: PR 번호 또는 URL
• strategy: merge | squash | squid (기본값: squid)

How This Skill Works

Manual workflow (This skill is NOT auto-invoked):

1. Read this guide
2. You call Task tool with Haiku subagent to merge PR
3. Haiku validates and merges the PR
4. Haiku reports result

Why manual: PR merge is an explicit action that requires user authorization.

When to Use This Skill

• After code review approval
• Ready to merge PR into main

Usage Example

When you want to merge a PR, you should call Task tool:

typescript
1Task({
2  subagent_type: "Bash",
3  model: "haiku",
4  description: "Merge PR (Haiku)",
5  prompt: `
6    Merge pull request with validation:
7
8    1. View PR info: gh pr view {pr} --json number,title,state,mergeable,headRefName,baseRefName
9    2. Verify: state=OPEN and mergeable=MERGEABLE
10    3. Check for worktree: git worktree list | grep {headRefName}
11    4. If worktree exists: bash scripts/worktree-cleanup.sh --path <worktree-path> --force
12    5. Merge with strategy {strategy}:
13       - gh pr merge {pr} --squash --delete-branch (if strategy is squid/squash)
14       - gh pr merge {pr} --merge --delete-branch (if strategy is merge)
15    6. Verify merge: gh pr view {pr} --json state,mergedAt,mergeCommit
16    7. Report: PR number, merge commit SHA
17
18    CRITICAL: Remove worktree BEFORE merge (--delete-branch fails if worktree exists)
19  `
20})

Strategy Mapping

• merge → --merge
• squash / squid → --squash

Rules

• NEVER merge without explicit user request
• Default strategy: squid (squash)
• NEVER merge if state ≠ OPEN or conflicts exist
• ALWAYS remove worktree before merge