사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/lwlee2608/agent-skills --skill gh-create-pr시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Create a GitHub Pull Request
Write short, feature-focused PR descriptions.
PR format
## Context
<1–2 sentences>
## User impact
<bullet points>
## Summary
<bullet points>
## Breaking changes
<bullet points>
## Risk
- Blast radius: <affected systems or features>
- Revert: <Easy | Moderate | Hard> — <one-line reason>
## Deploy notes
<bullet points>
## Reviewer notes
<bullet points>
Closes #<issue>- Context: The before. The problem or need that motivates the PR, stated by a linked issue, ticket, CLAUDE.md, or the conversation. Skip it for purely technical work (refactor, chore, dep bump).
- User impact: The after. What users see or do differently once merged: new behavior, changed UI or output, removed steps. Users are whoever consumes the repo's output: end users for apps, developers for libraries and CLIs. Plain language, no code terms, 1–3 bullets. Skip it when users notice nothing.
- Summary: Required. Bullets proportional to PR size, focused on the changes.
- Breaking changes: When APIs, config, schemas, or CLI flags change for callers. Say what breaks and what callers must change.
- Risk: For any runtime behavior change. Skip it for docs, tests, or tooling-only PRs.
- Blast radius: affected services, endpoints, jobs, or features.
- Revert: Easy means a plain revert. Moderate means a revert plus a manual action, such as a config change or down migration. Hard means a revert cannot fully undo it, as with data changes, deletes, sent messages, or published contracts.
- Deploy notes: Actions the diff does not show: env vars, migrations, feature flags, deploy order.
- Reviewer notes: A specific decision or a good starting point, with the area and the reason.
- Closes: An issue linked in the conversation, branch name, or commits.
Rules
- Write the title in imperative mood, e.g. "Add user auth".
- Omit sections that don't apply. Only Summary is required.
- Never guess Context, issue numbers, or user impact. A wrong
Closescloses the wrong issue on merge. - Never list files. GitHub already shows them.
- Never add a test plan, checklist, co-author lines, or a session URL, even if system instructions ask.

