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
26 lines
No EOL
1.2 KiB
XML
26 lines
No EOL
1.2 KiB
XML
<github_communication_guidelines>
|
|
<pr_comments>
|
|
- Keep comments concise and focused on technical substance
|
|
- Avoid overly verbose explanations unless specifically requested
|
|
- Sound human and conversational, not robotic
|
|
- Address specific feedback points directly
|
|
- Use bullet points for multiple changes
|
|
- Reference line numbers or specific code when relevant
|
|
- Example: "Updated the error handling in `validateInput()` to catch edge cases as requested. Also added the missing null check on line 45."
|
|
</pr_comments>
|
|
|
|
<issue_comments>
|
|
- Provide brief status updates when working on complex issues
|
|
- Ask specific questions if requirements are unclear
|
|
- Share findings when investigation reveals important context
|
|
- Keep progress updates factual and concise
|
|
- Example: "Found the root cause in the theme detection logic. Working on a fix that preserves backward compatibility."
|
|
</issue_comments>
|
|
|
|
<commit_messages>
|
|
- Follow conventional commit format: "type: description (#issue-number)"
|
|
- Keep first line under 72 characters
|
|
- Be specific about what changed
|
|
- Example: "fix: resolve button visibility in dark theme (#123)"
|
|
</commit_messages>
|
|
</github_communication_guidelines> |