Create GitHub Pull Request

VerifiedCaution

Commits current changes, pushes to remote, and creates a Pull Request. Use this skill when you've finished working and want to create a PR for review.

Sby Skills Guide Bot
DevelopmentIntermediate
606/2/2026
Claude Code
#git#pull-request#github#workflow

Recommended for

Our review

This skill automatically creates a GitHub Pull Request from the current working changes.

Strengths

  • Automates the full PR creation with a formatted title and body
  • Prevents accidental pushes on protected branches by suggesting a new branch
  • Includes issue references and a structured summary of changes

Limitations

  • Requires Git and GitHub CLI (gh) to be installed and configured
  • Only works with GitHub repositories
  • The PR body draft may need user review before finalization
When to use it

Use this skill when you have finished changes and want to quickly submit a Pull Request for review.

When not to use it

Avoid this skill if you are using a different Git platform (GitLab, Bitbucket) or need to manually configure advanced PR settings.

Security analysis

Caution
Quality score75/100

The skill automates git operations and GitHub PR creation, which involves pushing code and authenticating with GitHub; this is legitimate but powerful, and if abused or misconfigured could push unwanted changes or expose credentials.

Findings
  • Uses git push and gh pr create which can modify remote repositories and require network access.
  • No explicit mention of authentication or safety checks; assumes environment is properly configured.

Examples

Feature done – create PR
작업 끝났어 PR 올려줘
Request code review
리뷰 요청할게

name: github-pr description: 현재 작업 중인 변경사항을 Git 커밋하고 원격 저장소에 푸시한 뒤, "Pull Request(PR)"를 생성합니다. "작업 끝났어 PR 올려줘", "리뷰 요청할게" 등의 상황에서 사용하십시오.

Create GitHub PR

Creates a Pull Request for the current work.

Instructions

  1. Branch Check

    • If current branch is main or develop:
      • Ask user for branch name (e.g., feature/...).
      • git checkout -b <new-branch>
    • Else: Continue.
  2. Push Changes

    • Ensure all changes are committed.
    • git push origin HEAD
  3. Draft PR Body

    • Format: Markdown (Korean).
    • Content:
      • Link Issue (Closes #ID).
      • Summary of changes (Why & What).
      • Test/Verification status.
    • Show draft to user.
  4. Create PR

    • gh pr create --base develop --title "제목" --body "본문"
Related skills