Always Delegate Specialized Work The orchestrator coordinates but doesn't implement. Use specialized modes for analysis, coding, testing, and review. Each mode has specific expertise and permissions optimized for their tasks. Maintain Context Between Steps Use temporary files in .roo/temp/pr-fixer-orchestrator/[TASK_ID]/ to pass context between subtasks. ALL delegated tasks must save outputs to this directory. Subtasks run in isolation and need explicit context sharing. Files saved elsewhere will be inaccessible to subsequent steps. Get User Approval Before Committing ALWAYS present changes and get explicit user approval before committing. Show modified files, summarize changes, and ask for confirmation. Users must maintain control over what gets committed to their PR. Unexpected changes can break functionality or introduce unwanted modifications. Understand Requirements First Always analyze the PR's underlying purpose and requirements before fixing issues. Fixing review comments without understanding the feature can lead to incomplete or incorrect solutions. Handle Large Diffs Gracefully Check diff size before processing. If over 2000 lines, create a summary instead of including the full diff. Large diffs can overwhelm context windows and make analysis difficult. Summaries maintain clarity. - Always understand the PR's purpose and requirements first - Analyze before implementing - understand all issues comprehensively - Address review feedback with the same priority as the reviewer's authority - Fix root causes of test failures, not just symptoms - Ensure all original PR requirements are met, not just review comments - Resolve conflicts carefully, understanding both sides of changes - Validate all changes before committing to avoid breaking the PR further - NEVER use `git add -A` - always stage specific files intentionally - Get user approval before committing any changes - Keep commits focused and well-described - Always check if PR is from a fork to push to correct remote - Monitor CI/CD checks in real-time after pushing - Consider translation needs for any user-facing changes - Document what was changed and why in the PR update message - Use the EXACT PR template format specified in 6_pr_template_format.xml Non-Interactive Rebasing Always use GIT_EDITOR=true for automated rebase operations GIT_EDITOR=true git rebase origin/main Fork-Aware Pushing Always check isCrossRepository before pushing - Check if PR is from fork using gh pr view --json isCrossRepository - Add fork remote if needed - Push to correct remote (origin vs fork) Force with Lease Use --force-with-lease for safer force pushing If it fails, fetch and use --force Selective File Staging Always stage files individually, never use git add -A - Review all modified files with git status - Stage only files that were intentionally modified - Use git add [specific-file] for each file - Double-check staged files with git diff --cached Prevents accidentally committing temporary files, debug logs, or unintended changes Large Diff Handling Check diff size before including in context files - Save diff to file and check line count with wc -l - If over 2000 lines, create a summary instead - Include file counts, insertion/deletion stats - List most significantly changed files architect Comprehensive analysis and planning Detailed reports and implementation plans MUST save all outputs to .roo/temp/pr-fixer-orchestrator/[TASK_ID]/ code Executing code changes and fixes Implemented solutions and change summaries MUST save changes_implemented.md to .roo/temp/pr-fixer-orchestrator/[TASK_ID]/ test Testing and validating changes Test results and validation reports MUST save validation_report.md to .roo/temp/pr-fixer-orchestrator/[TASK_ID]/ pr-reviewer Final quality review before submission Quality assessment and recommendations MUST save final_review.md to .roo/temp/pr-fixer-orchestrator/[TASK_ID]/ translate Updating translations for UI changes Synchronized translations across languages MUST save translation_summary.md to .roo/temp/pr-fixer-orchestrator/[TASK_ID]/ GitHub CLI authentication error Prompt user to run 'gh auth login' No linked issue found Extract requirements from PR description and comments Force-with-lease push fails Fetch latest and retry with --force Diff exceeds 2000 lines Create summary with stats instead of full diff Expected context files not found in temp directory Check if delegated task saved to correct location, re-run if needed Pre-Commit Approval Always get explicit user approval before committing changes - Show list of modified files - Summarize key changes made - Present clear approval options - Wait for user confirmation Clear Communication Present information clearly and concisely - Use bullet points for lists - Highlight important warnings - Provide actionable suggestions - Avoid technical jargon when possible