GitHub PR Creation

VerifiedSafe

Analyzes branch changes and creates a GitHub Pull Request using the project's PR template.

Sby Skills Guide Bot
DevelopmentIntermediate
7/28/2026
Claude Code
#pull-request#git-workflow#github-cli#commit-conventions#korean

Recommended for

Automated summary

Analyzes the current branch's changes and creates a GitHub pull request via gh, filling in the project's PR template and deriving the issue number from the branch name.

Strengths

  • Automatically parses the issue number from the <type>/<issue#>-<slug> branch pattern and puts it in the body as 'Resolves : #n' instead of the title
  • Writes title and body in Korean following a strict convention (type(scope): summary) and strips HTML guidance comments from the template
  • Enforces a local iOS and Android E2E gate with pnpm test:e2e:app before opening the PR, and halts if it is not confirmed
  • Sticks to facts found in the diff and commit history rather than guessing

Limitations

  • Tightly coupled to this repository: relies on .github/PULL_REQUEST_TEMPLATE.md, .maestro/README.md, the main base branch and an internal branch-naming scheme
  • Assumes an authenticated gh CLI and, for the native E2E check, a running simulator and Metro — the run may have to be handed off to the user
  • All output is in Korean, which does not suit non-Korean-speaking teams
When to use it

Use it when a branch is ready and you want a PR that conforms to the repo's template and conventions generated quickly.

When not to use it

Skip it on repositories that do not follow this PR template, branch naming scheme or main base branch, or when the PR must be written in another language.

Security analysis

Safe
Quality score92/100

The skill uses git inspection, gh pr create, and pnpm test commands for legitimate PR creation. It does not include destructive commands, credential exfiltration, obfuscated payloads, or network requests to untrusted endpoints. The only remote action is creating a pull request on the existing repository, which is expected and low-risk.

No concerns found

How this analysis is made

Examples

Créer la PR de la branche courante
PR 만들어줘
PR après un correctif
/pr — feat/42-login-flow 브랜치 변경사항으로 PR 만들어줘
PR sans numéro d'issue
/pr chore/setup-ci 브랜치 PR 올려줘. 이슈 번호는 없어

name: pr description: | Creates a GitHub Pull Request by analyzing branch changes and filling in the project PR template. TRIGGER when: user invokes /pr directly, or says 'PR 만들어줘', 'PR 작성해줘'.

PR 생성

현재 브랜치의 변경사항을 분석하여 프로젝트 PR 템플릿(.github/PULL_REQUEST_TEMPLATE.md)에 맞는 Pull Request를 생성합니다.

작업 절차

  1. git branch --show-current 로 브랜치명을 확인하고 이슈 번호를 추출한다.
    • 패턴 <type>/<issue#>-<slug> (예: feat/2-init-setup) 에서 첫 / 와 다음 - 사이의 숫자가 이슈 번호.
    • 숫자가 없으면(chore/<slug> 형태) 묻지 말고 이슈 번호 없이 작성한다.
  2. git log <base>...HEAD --oneline 과 git diff <base>...HEAD 로 변경사항 전체를 파악한다.
  3. 앱 E2E 사전 체크 — 네이티브 앱 E2E 는 CI 에 없으므로 PR 생성 전 로컬 통과를 확인한다.
    • 변경이 md·웹 전용(*.md · docs/** · e2e/** · playwright.config.ts 등)뿐이면 생략.
    • 네이티브 관련 변경(컴포넌트·라우팅·네이티브 모듈 등)이 있으면, .maestro/README.md 의 "PR 전 로컬 체크" 절차대로 iOS·Android 둘 다 pnpm test:e2e:app 통과를 사용자에게 확인한다(시뮬레이터/Metro 필요 — 자동 실행 불가 시 사용자에게 실행을 요청). 미통과·미확인이면 PR 을 만들지 않고 멈춘다.
  4. 아래 형식으로 제목/본문을 작성한다.
  5. push가 필요하면 먼저 push한 뒤 gh pr create 로 생성한다.

제목 형식

<type>(<scope>): <한 줄 요약 (한글)>
  • 예: feat(app): 로그인 화면 추가, chore: 프로젝트 초기 셋업 보강
  • type 소문자, scope 선택.
  • 이슈 번호는 제목에 박지 않는다 — 본문 Resolves : #<번호> 가 자동 link/close 처리.

본문 형식

섹션 제목 + 내용만 넣는다. 안내용 HTML 주석(<!-- -->)은 본문에 포함하지 않는다.

## 관련 이슈

- Resolves : #<이슈번호>     <!-- 이슈 번호가 없으면 `- 해당 없음` -->

## 작업 사항

- <이 PR에서 수행한 작업을 bullet 으로, 한글로>

## 참고 사항

- <리뷰어가 알아야 할 맥락/주의사항. 없으면 `-` 그대로 둔다>
  • 모든 내용 한글로 작성.
  • 추측하지 말고 코드와 커밋 이력에서 파악된 사실만 기재한다.
  • 이슈 번호가 없으면 관련 이슈 섹션을 - 해당 없음 으로 두고 그대로 진행한다(묻지 않는다).

실행

gh pr create --title "<title>" --body "<filled template>"
  • base 브랜치는 main.

상세 컨벤션 (Branch · Commit · PR · Issue 통합): docs/conventions/git.md

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/github-pr-creation-ms47vo8h/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/github-pr-creation-ms47vo8h' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/github-pr-creation-ms47vo8h/download' --output '.skill-downloads/github-pr-creation-ms47vo8h/SKILL.md.part' && mv '.skill-downloads/github-pr-creation-ms47vo8h/SKILL.md.part' '.skill-downloads/github-pr-creation-ms47vo8h/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/github-pr-creation-ms47vo8h/SKILL.md' && test -s '.skill-downloads/github-pr-creation-ms47vo8h/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/github-pr-creation-ms47vo8h' '.claude/skills/pr'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/github-pr-creation-ms47vo8h'

openskills read 'github-pr-creation-ms47vo8h'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/github-pr-creation-ms47vo8h/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills