{"meta":{"title":"Pull request assistant","intro":"Generate comprehensive pull request descriptions and reviews.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/tutorials","title":"Tutorials"},{"href":"/en/copilot/tutorials/customization-library","title":"Customization library"},{"href":"/en/copilot/tutorials/customization-library/custom-instructions","title":"Custom instructions"},{"href":"/en/copilot/tutorials/customization-library/custom-instructions/pull-request-assistant","title":"Pull request assistant"}],"documentType":"article"},"body":"# Pull request assistant\n\nGenerate comprehensive pull request descriptions and reviews.\n\n> \\[!NOTE]\n>\n> * The examples in this library are intended for inspiration—you are encouraged to adjust them to be more specific to your projects, languages, and team processes.\n> * For community-contributed examples of custom instructions for specific languages and scenarios, see the [Awesome GitHub Copilot Customizations](https://github.com/github/awesome-copilot/blob/main/docs/README.instructions.md) repository.\n> * You can apply custom instructions across different scopes, depending on the platform or IDE where you are creating them. For more information, see \"[About customizing GitHub Copilot responses](/en/copilot/concepts/prompting/response-customization).\"\n\nThe following example shows custom instructions to guide GitHub Copilot to create detailed pull request descriptions and provide constructive code reviews.\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## Further reading\n\n* [About customizing GitHub Copilot responses](/en/copilot/concepts/prompting/response-customization) - Overview of response customization in GitHub Copilot\n* [Add custom instructions for Copilot](/en/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions) - How to configure custom instructions\n* [Awesome GitHub Copilot Customizations](https://github.com/github/awesome-copilot/blob/main/README.md) - Repository of community-contributed custom instructions and other customizations for specific languages and scenarios"}