This file contains the official Roo Code PR template that must be used when creating pull requests.
All PRs must follow this exact format to ensure consistency and proper documentation.
The PR body must follow this exact Roo Code PR template with all required sections.
Replace placeholder content in square brackets with actual information.
### Related GitHub Issue
Closes: #[ISSUE_NUMBER]
### Roo Code Task Context (Optional)
[TASK_CONTEXT]
### Description
[DESCRIPTION_CONTENT]
### Test Procedure
[TEST_PROCEDURE_CONTENT]
### Pre-Submission Checklist
- [x] **Issue Linked**: This PR is linked to an approved GitHub Issue (see "Related GitHub Issue" above).
- [x] **Scope**: My changes are focused on the linked issue (one major feature/fix per PR).
- [x] **Self-Review**: I have performed a thorough self-review of my code.
- [x] **Testing**: New and/or updated tests have been added to cover my changes (if applicable).
- [x] **Documentation Impact**: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
- [x] **Contribution Guidelines**: I have read and agree to the [Contributor Guidelines](/CONTRIBUTING.md).
### Screenshots / Videos
[SCREENSHOTS_CONTENT]
### Documentation Updates
[DOCUMENTATION_UPDATES_CONTENT]
### Additional Notes
[ADDITIONAL_NOTES_CONTENT]
### Get in Touch
[DISCORD_USERNAME]
]]>
Valid GitHub CLI commands for creating PRs with the proper template
Create a PR using the filled template
The PR body should be saved to a temporary file first, then referenced with --body-file
Alternative: Create PR with inline body (for shorter content)
Use this only if the body content doesn't contain special characters that need escaping
Fork repository if user doesn't have push access
The --clone=false flag prevents cloning since we're already in the repo
PR titles should follow conventional commit format
fix: [brief description] (#[issue-number])
feat: [brief description] (#[issue-number])
docs: [brief description] (#[issue-number])
refactor: [brief description] (#[issue-number])
test: [brief description] (#[issue-number])
chore: [brief description] (#[issue-number])
How to fill in the template placeholders
The GitHub issue number being addressed
123
Optional Roo Code task links if used during development
https://app.roocode.com/share/task-abc123
_No Roo Code task context for this PR_
Detailed explanation of implementation approach
- Focus on HOW you solved the problem
- Mention key design decisions
- Highlight any trade-offs made
- Point out areas needing special review attention
Steps to verify the changes work correctly
- List specific test commands run
- Describe manual testing performed
- Include steps for reviewers to reproduce tests
- Mention test environment details if relevant
Visual evidence of changes for UI modifications
_No UI changes in this PR_
Documentation impact assessment
- [x] No documentation updates are required.
Any extra context for reviewers
_No additional notes_
Discord username for communication
@username