feat: add Issue Fixer Orchestrator mode

[MuriloFP]

Related GitHub Issue

Closes: #

Roo Code Task Context (Optional)

This PR was created using Roo Code's Issue Fixer Orchestrator mode to add itself to the system.

Description

This PR introduces a new Issue Fixer Orchestrator mode that coordinates the complete workflow for resolving GitHub issues from start to finish. The mode acts as a conductor, delegating specialized tasks to other modes while managing context and user approval checkpoints.

Key Implementation Details:

• 11-step workflow from issue analysis to PR creation and monitoring
• Delegation pattern using new_task tool to coordinate architect, code, test, translate, and pr-reviewer modes
• Context management through temporary files in .roo/temp/issue-fixer-orchestrator/[TASK_ID]/
• User approval gates at critical milestones (plan approval, review feedback handling)
• Full GitHub CLI integration for all GitHub operations
• Translation workflow automatically triggered for UI changes
• PR review feedback loop with option to iterate before final submission

Reviewers should pay attention to:

• The comprehensive XML workflow definition in 1_Workflow.xml
• The delegation patterns and context file management
• The integration with existing modes (architect, code, test, translate, pr-reviewer)
• The GitHub CLI usage patterns and error handling

Test Procedure

Manual Testing Steps:

1. Switch to the new issue-fixer-orchestrator mode in Roo Code
2. Provide a GitHub issue URL to test the workflow
3. Verify each step of the 11-step process:
   • Issue context retrieval and parsing
   • Delegation to architect mode for analysis
   • Plan presentation and approval flow
   • Code implementation delegation
   • Testing and verification steps
   • Translation handling (if applicable)
   • PR review and feedback processing
   • Branch creation and PR submission

Testing Environment:

• Requires GitHub CLI (gh) authentication
• Needs access to a GitHub repository with issues
• Should test with both bug fixes and feature requests

Pre-Submission Checklist

• Issue Linked: This PR adds a new orchestrator mode for issue resolution workflow.
• Scope: Changes are focused on adding the new mode and its comprehensive rule set.
• Self-Review: Performed thorough review of the mode definition and workflow steps.
• Testing: Manual testing completed with the mode creation and workflow validation.
• Documentation Impact: Mode includes comprehensive documentation in XML rule files.
• Contribution Guidelines: Follows established patterns for custom mode creation.

Screenshots / Videos

This is a backend mode addition with no UI changes. The mode will appear in the mode selector as "🔧 Issue Fixer Orchestrator".

Documentation Updates

• No documentation updates are required.

The mode is self-documenting through its comprehensive XML rule files and whenToUse description.

Additional Notes

Architecture Notes:

• This mode follows the established pattern of other orchestrator modes
• Uses the same XML rule structure as existing modes
• Integrates seamlessly with the current mode system
• Provides a complete end-to-end workflow for GitHub issue resolution

Future Enhancements:

• Could be extended to support multiple issue types or repositories
• May benefit from integration with project management tools
• Could include automated testing of the implemented solutions

Get in Touch

@MuriloFP

Available for questions and feedback on the implementation approach and workflow design.

---

Important

Introduces issue-fixer-orchestrator mode to manage GitHub issues end-to-end, with detailed workflows, best practices, and GitHub CLI integration.

• New Mode:
  • Adds issue-fixer-orchestrator mode to handle GitHub issues end-to-end.
  • Coordinates tasks like analysis, implementation, testing, and PR creation.
• Workflows:
  • Defined in 1_Workflow.xml, covering steps from issue parsing to PR monitoring.
  • Includes user approval checkpoints and translation handling.
• Best Practices:
  • 2_best_practices.xml outlines coding standards, testing, and translation requirements.
• Common Patterns:
  • 3_common_patterns.xml provides patterns for bug fixes and feature implementations.
• GitHub CLI Usage:
  • 4_github_cli_usage.xml details commands for issue handling and PR creation.
• PR Workflow:
  • 5_pull_request_workflow.xml describes PR preparation and creation steps.
• Testing Guidelines:
  • 6_testing_guidelines.xml emphasizes comprehensive testing strategies.
• Communication Style:
  • 7_communication_style.xml and 8_github_communication_guidelines.xml guide effective communication.
• Translation Handling:
  • 9_translation_handling.xml ensures all user-facing content is translated before PR creation.
• Mode Configuration:
  • Updates .roomodes to include the new orchestrator mode.

^{This description was created by for 4d7a20cc984bb2412e60569acefe1e382b5c0e9b. You can customize this summary. It will automatically update as commits are pushed.}