github-pr-best-practices
Create professional GitHub pull requests
๋ํ ๋ค์์์ ์ฌ์ฉํ ์ ์์ต๋๋ค: 1natsu172
Creating pull requests without clear standards leads to confusing reviews and delayed merges. This skill provides proven templates and guidelines for writing PR titles, descriptions, and formats following conventional commit standards. Supports both English and Japanese output.
์คํฌ ZIP ๋ค์ด๋ก๋
Claude์์ ์ ๋ก๋
์ค์ โ ๊ธฐ๋ฅ โ ์คํฌ โ ์คํฌ ์ ๋ก๋๋ก ์ด๋
ํ ๊ธ์ ์ผ๊ณ ์ฌ์ฉ ์์
ํ ์คํธํด ๋ณด๊ธฐ
"github-pr-best-practices" ์ฌ์ฉ ์ค์ ๋๋ค. Create a PR for adding user profile features with avatar upload and bio editing
์์ ๊ฒฐ๊ณผ:
- ## Summary
- - Add user profile customization features
- - Implement avatar upload with image processing
- - Add bio and social links editing
- ย
- ## Test plan
- - [ ] Test avatar upload and processing
- - [ ] Test bio editing with various markdown
- - [ ] Test social links validation
- - [ ] Test file size and format validation
๋ณด์ ๊ฐ์ฌ
์์ Pure documentation skill containing only markdown files. No executable code, network calls, filesystem access, or environment variable reads. This skill provides guidance templates and best practices for creating GitHub pull requests.
ํ์ง ์ ์
๋ง๋ค ์ ์๋ ๊ฒ
Standardize PR format
Apply consistent PR titles and descriptions across your team with conventional commit standards
Improve contribution quality
Guide contributors to write clear PR descriptions that speed up review time
Create bilingual PRs
Generate PR content in English or Japanese to support multilingual development teams
์ด ํ๋กฌํํธ๋ฅผ ์ฌ์ฉํด ๋ณด์ธ์
Create a pull request for a new feature that adds OAuth2 authentication with the following commits: 'feat(auth): add OAuth2 login' and 'feat(config): add provider settings'. Use English output.
Write a PR description for fixing a race condition in session management. The root cause was concurrent requests modifying session state. Use Japanese output.
Create a PR description for migrating API from v1 to v2. Include breaking changes about response format and user ID type changes. Follow the complex change template.
Create a PR for updating API documentation. The changes include new endpoints, authentication examples, and fixed parameter descriptions. Use the documentation template.
๋ชจ๋ฒ ์ฌ๋ก
- Follow conventional commit format with type, optional scope, and clear description
- Keep PR summaries to 1-3 bullet points explaining what and why, not how
- Always include a test plan with specific, actionable checkbox items
ํผํ๊ธฐ
- Using emojis in PR titles or descriptions breaks professional standards
- Vague descriptions like 'Updated stuff' provide no context for reviewers
- Creating PRs without analyzing all commits misses important changes
์์ฃผ ๋ฌป๋ ์ง๋ฌธ
What tools support this skill?
What conventional commit types are supported?
How do I switch between English and Japanese?
Is my data safe when using this skill?
Why are my PRs rejected by CI?
How is this different from git-analysis skill?
๊ฐ๋ฐ์ ์ธ๋ถ ์ ๋ณด
์์ฑ์
1natsu172๋ผ์ด์ ์ค
MIT
๋ฆฌํฌ์งํ ๋ฆฌ
https://github.com/1natsu172/dotfiles/tree/master/.claude/skills/github-pr-best-practices์ฐธ์กฐ
master
ํ์ผ ๊ตฌ์กฐ