← ClaudeAtlas

prlisted

Create a GitHub Pull Request with auto-detected base branch, type/mode labels, self-assign, and auto-reviewer selection. Use when the user says "pr", "PR 만들어", "풀리퀘", or wants to create a pull request.
teamBuzzle/asdf · ★ 1 · Code & Development · score 65
Install: claude install-skill teamBuzzle/asdf
Create a GitHub Pull Request for the current branch with full automation. ## Steps ### 1. Gather branch info Run these commands in parallel: ```bash # Current branch name git rev-parse --abbrev-ref HEAD # Detect the base branch (where this branch was created from) git log --oneline --decorate --all --ancestry-path HEAD..main --merges 2>/dev/null | head -1 # Fallback: find the merge-base with main git merge-base HEAD main # Get the current user's GitHub username gh api user --jq '.login' # Pick the reviewer: one of the review pool at random, excluding yourself gh api repos/{owner}/{repo}/collaborators --jq '.[].login' # Check if there are unpushed commits git status git log --oneline origin/$(git rev-parse --abbrev-ref HEAD)..HEAD 2>/dev/null ``` Determine the **base branch**: Use `git merge-base --fork-point main HEAD` or `git merge-base main HEAD` to find where the current branch diverged from. The base branch is `main` unless the branch was created from another feature branch (detect via branch naming or merge-base). ### 2. Analyze changes ```bash # All commits on this branch since diverging from base git log --oneline $(git merge-base main HEAD)..HEAD # Full diff against base git diff $(git merge-base main HEAD)..HEAD --stat git diff $(git merge-base main HEAD)..HEAD ``` Read all the commits and the diff carefully to understand: - What was changed and why - The scope and risk of the changes - Whether tests, lint, or build were affected ### 3. Select labels