mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-10-08 03:07:53 +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
14 lines
No EOL
631 B
XML
14 lines
No EOL
631 B
XML
<best_practices>
|
|
- Always read the entire issue and all comments before starting
|
|
- Follow the project's coding standards and patterns
|
|
- Make minimal changes for bug fixes (don't refactor unnecessarily)
|
|
- Test thoroughly - both automated and manual testing
|
|
- Document complex logic with comments
|
|
- Keep commits focused and well-described
|
|
- Reference the issue number in commits
|
|
- Verify all acceptance criteria are met
|
|
- Consider performance and security implications
|
|
- Update documentation when needed
|
|
- Add tests for any new functionality
|
|
- Check for accessibility issues (for UI changes)
|
|
</best_practices> |