Menu
Generate PR title, body, and labels from commits since the base branch, then create the PR on GitHub.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Create Git commits by splitting changes into logical units following project conventions. Handles Git Flow automatically — detects develop branch and checks out a feature branch before committing.
Conduct an in-depth structured interview with the user to uncover non-obvious requirements, tradeoffs, and constraints, then produce a detailed implementation spec file.
For each inline PR review comment, judge whether it has been resolved in the current branch diff and reply with the resolving commit hash. Use after addressing PR feedback.
Run a structured checklist over changed files — DTO conventions, Java/Spring style, JPA/transaction correctness, test coverage, commit conventions, and security basics. Produces a ✓/⚠/✗ report.
Verify security vulnerabilities — hardcoded secrets, SQL injection, JWT validation, blacklist enforcement, sensitive logging, and authorization checks. Run before merging any auth or API-related changes.
| name | pr-draft |
| description | Generate PR title, body, and labels from commits since the base branch, then create the PR on GitHub. |
| allowed-tools | Bash(git *:*), Bash(bash *create-pr.sh:*), Bash(cat *:*), Bash(gh *:*), Read, Write |
Run all at once:
git branch --show-current
git log origin/develop..HEAD --oneline 2>/dev/null || git log --oneline -15
git diff origin/develop...HEAD --stat 2>/dev/null || git diff HEAD~5...HEAD --stat
git diff origin/develop...HEAD 2>/dev/null || git diff HEAD~5...HEAD
Also read the PR template:
cat .github/PULL_REQUEST_TEMPLATE.md
Search open issues to find the related one:
gh issue list --state open --limit 50
Match the most relevant issue by comparing issue titles and labels against the branch name and commit messages. Note the issue number for use in Steps 3–5.
Read ${CLAUDE_SKILL_DIR}/references/labels.md and select 1–2 appropriate labels.
Title — Generate 3 options:
fix ::, update ::, etc.)← 추천Body — Follow .github/PULL_REQUEST_TEMPLATE.md structure:
~하였습니다, ~되었습니다, ~추가하였습니다Close #N using the related issue number found in Step 1Start by copying the PR template as the base:
cp .github/PULL_REQUEST_TEMPLATE.md PR_BODY.md
Then fill in each section of PR_BODY.md with the generated content — do not change the section headers or structure. Display:
## 추천 PR 제목
1. title1
2. title2
3. title3 ← 추천
## 선택된 라벨
- label1, label2
## 관련 이슈
- #N: issue title
## PR 본문 미리보기
[body content]
Ask the user to confirm which title to use. If no answer, proceed with the recommended title.
bash "${CLAUDE_SKILL_DIR}/scripts/create-pr.sh" "<confirmed-title>" "PR_BODY.md" "<label1>,<label2>" "School-of-Company/Gwangju-talent-festival-Server" "@me"
After creation, display the PR URL.
Cleanup: remove PR_BODY.md.