pr-all-in-one

PR All-in-One

Overview

Streamlines commit-to-PR workflow with auto-commit, smart issue linking, and multi-language support. Handles the complete flow from uncommitted changes to published PR with intelligent branch management, logical commit grouping, and context-aware PR descriptions.

When to Use

• Any situation requiring PR creation
• When uncommitted changes exist
• When an existing PR needs updating
• When you want to handle branch creation and PR in one step
• When you want to auto-link Issue IDs to the PR

Usage

/pr-all-in-one [target-branch] [issue-id]

Examples:

• /pr-all-in-one - PR to default branch, issue ID from branch name
• /pr-all-in-one develop - PR to develop, issue ID from branch name
• /pr-all-in-one main ISSUE-12345 - PR to main with issue ID
• /pr-all-in-one ISSUE-12345 - PR to default branch with issue ID

Argument Parsing:

• target-branch: Branch name (main, develop, master, etc.)
• issue-id: Matches configured issue pattern (JIRA-123, #456, ENG-789, etc.)
• Arguments can be in any order
• If only one argument provided, checks if it's an issue pattern first

Configuration

Location: .claude/pr-config.json

First-time run: Interactive setup flow guides you through configuration.

See configuration-guide.md for:

• All configuration options
• Setup wizard walkthrough
• Example configurations

Workflow (9 Steps)

┌─────────────────────────────────────────────────┐
│              Workflow Execution                 │
└─────────────────────────────────────────────────┘

Step 1: Parse arguments
├── Issue pattern → issue ID
├── Branch name → target branch
└── Defaults from config

Step 2: Check git status & branch
├── git status (uncommitted changes)
└── git branch --show-current

Step 3: Handle main branch case
├── If on target branch with changes
│   ├── Analyze changes for branch name
│   ├── Create new branch: git checkout -b <type>/<description>
│   └── Proceed to Step 4
└── If on target branch without changes → Exit

Step 4: Auto-commit changes
├── Analyze with git diff
├── Group by feature/purpose
└── For each group:
    ├── git add <related-files>
    ├── Conventional commit message (English)
    └── NO AI signature/Co-Authored-By

Step 5: Push to remote
└── git push -u origin <branch> (if needed)

Step 6: Check existing PR
└── gh pr view --json url,title,body

Step 7: Update existing PR (if exists)
├── Analyze all commits: git log <target>..HEAD
├── Read prLanguage from .claude/pr-config.json
├── Select template based on prLanguage:
│   ├── "en" → English Template
│   ├── "ko" → Korean Template
│   └── "bilingual" → Bilingual Template
├── Generate title:
│   ├── "en"/"bilingual" → English title
│   └── "ko" → Korean title
├── Generate body with selected template
├── Merge with .github/pull_request_template.md (if exists)
├── NO AI signature
└── gh pr edit --title --body

Step 8: Create new PR (if not exists)
├── Analyze all commits
├── Read prLanguage from .claude/pr-config.json
├── Select template based on prLanguage:
│   ├── "en" → English Template
│   ├── "ko" → Korean Template
│   └── "bilingual" → Bilingual Template
├── Generate title:
│   ├── "en"/"bilingual" → English (e.g., "feat: add auth")
│   └── "ko" → Korean (e.g., "feat: add authentication")
├── Generate body with selected template + commit analysis
├── Merge with project template if exists
├── NO AI signature
└── gh pr create --draft --base <target>

Step 9: Return PR URL
└── If UI changes detected → suggest screenshots