pr
12
总安装量
12
周安装量
#26886
全站排名
安装命令
npx skills add https://github.com/jacehwang/skills --skill pr
Agent 安装分布
claude-code
12
opencode
10
antigravity
10
github-copilot
10
codex
10
kimi-cli
10
Skill 文档
Context
- Current branch: !
git branch --show-current - Uncommitted changes: !
git status --short - Remote tracking status: !
git status -sb | head -1 - Existing PR: !
gh pr view --json number,title,url 2>/dev/null || echo "none" - Commits since main: !
git log main..HEAD --oneline - Full commit details: !
git log main..HEAD --format="- %h: %s" - Changes summary: !
git diff main...HEAD --stat | tail -5
Your task
Create a new PR or update an existing PR for the current branch.
Pre-checks
- Uncommitted changes: If there are uncommitted changes, warn the user and ask if they want to commit first
- Push status: If the branch is not pushed or behind remote, push it first with
git push -u origin <branch>
Behavior
If NO existing PR â Create new PR
Use gh pr create with title, body, and assignee.
If PR already exists â Update PR body only
Use gh pr edit to update the body with the latest commit list. Do NOT change the title.
PR Format
Title (for new PRs only)
Rules:
- English only – Never use Korean in titles
- 40 chars max (excluding prefix) – Be extremely concise
- Use short verbs: Add, Fix, Update, Remove, Refactor
- Ticket prefix: If the branch name contains a ticket identifier (pattern: letters + hyphen + numbers, e.g.,
ABC-123orproj-1), extract it, uppercase it, and prepend as[ABC-123]prefix to the title
Format:
- With ticket:
[TASK-123] Concise description - Without ticket:
Concise description
Ticket detection examples:
- Branch
TASK-123â[TASK-123] - Branch
TASK-123-add-featureâ[TASK-123] - Branch
feature/JIRA-456-fix-bugâ[JIRA-456] - Branch
proj-42â[PROJ-42] - Branch
proj-42-fix-layoutâ[PROJ-42] - Branch
add-new-featureâ no prefix
Examples:
[TASK-123] Add proposal management[FE-42] Fix auth flow[PROJ-42] Fix layout issue(lowercase branch â uppercased prefix)Update Claude Code config(no ticket in branch)
Body
íêµì´ë¡ ìì±. Use this format with HEREDOC:
Creating new PR:
gh pr create --title "[TASK-123] Description" --assignee @me --body "$(cat <<'EOF'
## ìì½
<ì´ PRì´ íë ì¼ì ê°ëµí ì¤ëª
>
## ë³ê²½ì¬í
<ì»¤ë° í´ìì í¨ê» 목ë¡ì¼ë¡ ìì±>
ð¤ Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Updating existing PR:
gh pr edit --body "$(cat <<'EOF'
## ìì½
<ì´ PRì´ íë ì¼ì ê°ëµí ì¤ëª
- 기존 ìì½ ì ì§ ëë íì¥>
## ë³ê²½ì¬í
<모ë ì»¤ë° í´ìì í¨ê» 목ë¡ì¼ë¡ ìì± - ì ì²´ 목ë¡>
ð¤ Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"
Guidelines
- Analyze ALL commits in the branch (not just the latest) to understand the full scope
- Titleì ìì´ë¡, Bodyë íêµì´ë¡ ìì±
- Include all commit hashes in the body for traceability
- When updating, preserve the intent of the original summary while incorporating new changes