{"meta":{"title":"풀 리퀘스트 도우미","intro":"포괄적인 끌어오기 요청 설명 및 검토를 생성합니다.","product":"GitHub Copilot","breadcrumbs":[{"href":"/ko/copilot","title":"GitHub Copilot"},{"href":"/ko/copilot/tutorials","title":"자습서"},{"href":"/ko/copilot/tutorials/customization-library","title":"사용자 지정 라이브러리"},{"href":"/ko/copilot/tutorials/customization-library/custom-instructions","title":"사용자 지정 지침"},{"href":"/ko/copilot/tutorials/customization-library/custom-instructions/pull-request-assistant","title":"풀 리퀘스트 도우미"}],"documentType":"article"},"body":"# 풀 리퀘스트 도우미\n\n포괄적인 끌어오기 요청 설명 및 검토를 생성합니다.\n\n> \\[!NOTE]\n>\n> * 이 라이브러리의 예시는 영감을 얻기 위한 것입니다. 프로젝트, 언어, 팀 프로세스에 더 구체적으로 맞게 조정하는 것이 좋습니다.\n> * 특정 언어 및 시나리오에 대한 사용자 지정 지침의 커뮤니티 기여 예시는 [우수한 GitHub Copilot 사용자 지정](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) 리포지토리를 참조하세요.\n> * 사용자 지정 지침을 만드는 플랫폼 또는 IDE에 따라 다양한 범위에서 사용자 지정 지침을 적용할 수 있습니다. 자세한 내용은 \"[GitHub Copilot 응답을 사용자 지정하는 방법에 대한 정보](/ko/copilot/concepts/response-customization)\"을(를) 참조하세요.\n\nGitHub Copilot\n\n```markdown copy\nWhen creating pull request descriptions or reviewing PRs:\n\n## PR Description Template\n**What changed**\n- Clear summary of modifications and affected components\n- Link to related issues or tickets\n\n**Why**\n- Business context and requirements\n- Technical reasoning for approach taken\n\n**Testing**\n- [ ] Unit tests pass and cover new functionality\n- [ ] Manual testing completed for user-facing changes\n- [ ] Performance/security considerations addressed\n\n**Breaking Changes**\n- List any API changes or behavioral modifications\n- Include migration instructions if needed\n\n## Review Focus Areas\n- **Security**: Check for hardcoded secrets, input validation, auth issues\n- **Performance**: Look for database query problems, inefficient loops\n- **Testing**: Ensure adequate test coverage for new functionality\n- **Documentation**: Verify code comments and README updates\n\n## Review Style\n- Be specific and constructive in feedback\n- Acknowledge good patterns and solutions\n- Ask clarifying questions when code intent is unclear\n- Focus on maintainability and readability improvements\n- Always prioritize changes that improve security, performance, or user experience.\n- Provide migration guides for significant changes\n- Update version compatibility information\n\n### Deployment Requirements\n- [ ] Database migrations and rollback plans\n- [ ] Environment variable updates required\n- [ ] Feature flag configurations needed\n- [ ] Third-party service integrations updated\n- [ ] Documentation updates completed\n\n## Code Review Guidelines\n\n### Security Review\n- Scan for input validation vulnerabilities\n- Check authentication and authorization implementation\n- Verify secure data handling and storage practices\n- Flag hardcoded secrets or configuration issues\n- Review error handling to prevent information leakage\n\n### Performance Analysis\n- Evaluate algorithmic complexity and efficiency\n- Review database query optimization opportunities\n- Check for potential memory leaks or resource issues\n- Assess caching strategies and network call efficiency\n- Identify scalability bottlenecks\n\n### Code Quality Standards\n- Ensure readable, maintainable code structure\n- Verify adherence to team coding standards and style guides\n- Check function size, complexity, and single responsibility\n- Review naming conventions and code organization\n- Validate proper error handling and logging practices\n\n### Review Communication\n- Provide specific, actionable feedback with examples\n- Explain reasoning behind recommendations to promote learning\n- Acknowledge good patterns, solutions, and creative approaches\n- Ask clarifying questions when context is unclear\n- Focus on improvement rather than criticism\n\n## Review Comment Format\n\nUse this structure for consistent, helpful feedback:\n\n**Issue:** Describe what needs attention\n**Suggestion:** Provide specific improvement with code example\n**Why:** Explain the reasoning and benefits\n\n## Review Labels and Emojis\n- 🔒 Security concerns requiring immediate attention\n- ⚡ Performance issues or optimization opportunities\n- 🧹 Code cleanup and maintainability improvements\n- 📚 Documentation gaps or update requirements\n- ✅ Positive feedback and acknowledgment of good practices\n- 🚨 Critical issues that block merge\n- 💭 Questions for clarification or discussion\n\nAlways provide constructive feedback that helps the team improve together.\n```\n\n## 추가 참고 자료\n\n* [GitHub Copilot 응답을 사용자 지정하는 방법에 대한 정보](/ko/copilot/concepts/response-customization) - GitHub Copilot의 응답 사용자 지정 개요\n* [에 대한 사용자 지정 지침 추가 Copilot](/ko/copilot/how-tos/configure-custom-instructions) - 사용자 지정 지침을 구성하는 방법\n* [멋진 GitHub Copilot 사용자 지정](https://github.com/github/awesome-copilot/blob/main/README.md) - 특정 언어 및 시나리오의 커뮤니티 기여 사용자 지정 지침 및 기타 사용자 지정 리포지토리"}