Generate a pull request description for the following changes.
PR Context
- Type:
{{pr_type}} - Related Issue/Ticket:
{{issue_reference}} - Breaking Changes:
{{breaking_changes}}
Code Changes Summary
{{changes_summary}}
PR Description Format
Title
[Type]: Brief description (50 chars max)
Examples:
- feat: Add user authentication flow
- fix: Resolve race condition in payment processing
- refactor: Simplify data transformation logic
Description
## Summary
Brief explanation of what this PR does (2-3 sentences)
## Motivation
Why is this change needed? Link to issue/discussion.
## Changes
- Bullet point list of changes
- Organized by file or feature area
- Highlight important changes
## Type of Change
- Bug fix (non-breaking)
- New feature (non-breaking)
- Breaking change
- Documentation update
- Refactoring
- Performance improvement
- Test coverage
## Testing
How was this tested?
- Unit tests added/updated
- Integration tests added/updated
- Manual testing performed
Test instructions:
- Step to reproduce
- Expected result
## Screenshots (if UI changes)
Before After image image## Checklist
- Code follows project style guidelines
- Self-review completed
- Documentation updated (if needed)
- No new warnings introduced
- Tests pass locally
## Deployment Notes
Any special deployment considerations:
- Migrations needed?
- Feature flags?
- Environment variables?
- Dependencies updated?
## Related PRs
- Link to related PRs if part of larger feature
Variables 4
PR Type
e.g., Feature, Bug fix, Refactor, Hotfix{{pr_type}}Related Issue/Ticket
e.g., JIRA-123, #456, Fixes #789{{issue_reference}}Breaking Changes
e.g., Yes - API response format changed, No breaking changes{{breaking_changes}}Changes Summary
Describe what you changed: e.g., Added new UserService class, Updated authentication middleware, Fixed null pointer in OrderProcessor...{{changes_summary}}You are a senior developer who writes excellent PR descriptions. Be concise but complete.