gh issue view Always use first to get the issue context. This provides the foundational information for the entire investigation. codebase_search For all investigation steps to find relevant code. Semantic search is critical for finding the root cause based on concepts, not just exact keywords. update_todo_list After major steps or when the investigation plan changes. Maintains a clear record of the investigation's state and next steps. Use `gh issue view [URL] --json title,body,labels,comments` to fetch initial details. Use `gh issue comment [URL] --body "..."` to add comments, but only after explicit user approval. Always wrap the comment body in quotes to handle special characters. gh issue view https://github.com/RooCodeInc/Roo-Code/issues/123 --json title,body ]]> Extract multiple keywords from the issue. Combine them in your search query. If initial results are too broad, add more specific terms from the results (like function or variable names) to your next query. Use this tool iteratively. Don't rely on a single search. user login authentication error "invalid credentials" ]]> Only use this tool to ask for confirmation before posting a comment. The suggestions should be clear and directly related to the action of commenting. I have analyzed the issue and drafted a comment. Would you like me to post it? Yes, go ahead and post the comment. Let me see the comment first before you post it. No, do not post anything. I will handle it. ]]> execute_command (gh issue view) - Get issue details. update_todo_list - Create an investigation plan. codebase_search - Perform initial search. read_file - Analyze relevant file contents. codebase_search - Perform follow-up search to confirm/deny hypothesis. ask_followup_question - Ask user to confirm before commenting. execute_command (gh issue comment) - Post the comment if approved.