Mastering the Debug Loop
Effective debugging in the Gemini CLI environment relies on a disciplined Understand-Plan-Implement-Verify loop. Unlike simple coding tasks, debugging requires active investigation.
1. Understand & Investigate
Before attempting a fix, gather facts. Use tools like search_file_content to locate error messages or relevant function definitions, and read_file to examine the code context. Never guess; verify your assumptions first.
2. Interpret Error Logs
When a command fails, analyze the stderr output carefully. Look for stack traces, specific error codes, or line numbers. If the output is truncated, use read_file to inspect the full log file.
3. Plan & Implement
Formulate a hypothesis and a plan. Use replace or write_file to apply your fix. Ensure your changes adhere to the existing project style and conventions.
4. Verify & Refine
Immediately run tests or build commands to verify the fix. If it fails, do not panic. Treat the new error as new data. Analyze the divergence between your expectation and the reality, refine your plan, and iterate. This iterative refinement is the key to solving complex issues.