mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-08-28 05:27:24 +00:00
2ea26637d7
* Add issue writer mode with detailed templates for bug reports and feature proposals * Refactor issue-writer mode to enhance role definition and instructions for creating GitHub issues * Add steps for searching GitHub Discussions and documenting related issues in the issue creation process * Add Issue Fixer mode with detailed workflow for resolving GitHub issues * Enhance Issue Fixer mode with detailed workflows for PR reviews and issue handling * Refactor Issue Fixer and Issue Worker modes to enhance workflow orchestration and implementation processes. Updated role definitions, added detailed workflows for issue resolution, and improved context management and communication guidelines. * Enhance issue-worker mode with branch verification steps and detailed instructions for ensuring correct branch setup before implementation. Updated workflow to include branch context in design planning and final verification processes. * Enhance pull request creation and verification workflow with detailed steps for branch verification, commit checks, and comprehensive PR status monitoring. Improved instructions for ensuring successful PR creation and linking to original issues. * feat: Add Issue Writer and Issue Fixer modes with comprehensive workflows - Add Issue Writer mode for creating well-structured GitHub issues - Add Issue Fixer mode for implementing fixes from GitHub issues - Include detailed workflow rules and best practices for both modes - Add GitHub MCP tool usage guidelines - Include PR workflow and communication guidelines
30 lines
No EOL
937 B
XML
30 lines
No EOL
937 B
XML
<pull_request_workflow>
|
|
<preparation>
|
|
1. Ensure all changes are committed with proper message format
|
|
2. Push to appropriate branch (fork or direct)
|
|
3. Prepare comprehensive PR description
|
|
4. Get user approval before creating PR
|
|
</preparation>
|
|
|
|
<pr_title_format>
|
|
- Bug fixes: "fix: [description] (#[issue-number])"
|
|
- Features: "feat: [description] (#[issue-number])"
|
|
- Follow conventional commit format
|
|
</pr_title_format>
|
|
|
|
<pr_description_template>
|
|
Must include:
|
|
- Link to issue (Fixes #[number])
|
|
- Detailed description of changes
|
|
- Testing performed
|
|
- Verification of acceptance criteria
|
|
- Checklist items
|
|
- Screenshots/demos if applicable
|
|
</pr_description_template>
|
|
|
|
<after_creation>
|
|
1. Comment on original issue with PR link
|
|
2. Inform user of successful creation
|
|
3. Provide next steps and tracking info
|
|
</after_creation>
|
|
</pull_request_workflow> |