pr

Generate GitHub-ready pull request titles and markdown bodies from branch diffs.

8|2|Updated May 3, 2026
One-click install
npx skills add https://github.com/ejoongseok/claude-settings --skill pr-ejoongseok
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/ejoongseok/claude-settings/tree/main/claude-code/skills/pr
Command: npx skills add https://github.com/ejoongseok/claude-settings --skill pr-ejoongseok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

프로젝트 PR을 만들 때 변경 내용을 빠짐없이 요약해 형식에 맞는 제목과 본문을 작성하는 데 드는 시간을 줄여줍니다.

Core Features & Use Cases

  • Git diff 기반 자동 요약: 현재 브랜치의 변경 파일과 diff를 분석해 리뷰어가 이해하기 쉬운 PR 초안을 만듭니다.
  • PR 템플릿 정합성: .github/PULL_REQUEST_TEMPLATE.md를 우선 감지해 그 형식에 맞게 제목/본문을 구성합니다(없으면 기본 CONTRACT 구조).
  • 팀 스타일 참고: 최근 PR(3~5개)을 조회해 실제 작성 톤과 수준을 따라 초안을 생성합니다.
  • 조건부 품질 가드레일: 변경 규모가 클 때는 요약 모드 및 분할 PR 권고를 포함해 리뷰 부담을 줄이도록 설계되어 있습니다.

Quick Start

pr 스킬을 실행해 현재 브랜치의 변경 사항을 바탕으로 PR에 붙여넣을 제목과 마크다운 본문을 생성해달라고 요청하세요.

Frequently Asked Questions about pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically generate a pull request title and markdown body from a git diff?

Generate a pull request draft by analyzing your current branch's git diff, commit history, and changed files to output a markdown body and title. The tool reviews recent pull requests to match your team's specific formatting tone and structure.

How does PR template compliance work when drafting pull request descriptions?

PR template compliance works by detecting a `.github/PULL_REQUEST_TEMPLATE.md` file and structuring the generated markdown body to match its exact format. If no template exists, it defaults to a standard structured format for the pull request.

Can I use this to draft a pull request for a large feature branch with many changed files?

You can use this for a large feature branch, as it includes quality guardrails that activate when the change scale is large. It provides a summary mode and recommends splitting the pull request to reduce reviewer burden and maintain code review quality.

What is the best way to write a pull request summary that matches my team's formatting style?

The best way to match your team's formatting style is to reference recent pull request history. The tool queries the last three to five pull requests to learn the actual writing tone and level of detail, then applies that style to your generated draft.

Does the tool directly create or push the pull request to GitHub?

The tool does not directly create or push the pull request to GitHub. It performs output-only generation, providing you with the title and markdown body to copy and paste into your repository.

How do I include an issue number in a generated pull request title?

Include an issue number in your branch name, and the pull request generation process will detect it. The tool analyzes the branch name alongside the git diff to incorporate the issue tracking reference into the final markdown output.