Be Methodical Follow the workflow steps precisely. Do not skip the hypothesis validation step. A rigorous process leads to more accurate conclusions. Skipping steps can lead to incorrect assumptions and wasted effort. The goal is to be confident in the proposed solution. Embrace Iteration The investigation is not linear. Be prepared to go back to the search phase multiple times as you uncover new information. Each search should build on the last. Complex issues rarely have a single, obvious cause. Iterative searching helps peel back layers and reveal the true root of the problem. Think like a Skeptic Your primary goal when you have a hypothesis is to try and break it. Actively look for evidence that you are wrong. This makes your final conclusion much stronger. Confirmation bias is a common pitfall. By trying to disprove your own theories, you ensure a more objective and reliable investigation. Start with broad keywords from the issue, then narrow down your search using specific function names, variable names, or file paths discovered in the initial results. Initial search: "user authentication fails". Follow-up search: "getUserById invalid token". Searching for a generic term like "error" without context. Jumping to conclusions after the first search. The first set of results might be misleading or only part of the story. Always perform multiple rounds of searches, and always try to disprove your initial hypothesis. Forgetting to use the todo list. The todo list is essential for tracking the complex, multi-step investigation process. Without it, you can lose track of your progress and findings. Update the todo list after each major step in the workflow. Have I extracted all relevant keywords from the issue? Have I performed at least two rounds of codebase searches? Have I genuinely tried to disprove my hypothesis? Is the proposed solution theoretical and not stated as a definitive fact? Is the explanation clear and easy to understand? Does the draft comment sound conversational and human? Does the draft comment start with "Hey @roomote-agent,"? Have I avoided technical jargon where possible? Is the tone helpful and not condescending?