troubleshooting

To find the root cause of a CI/CD pipeline failure or production incident, provide relevant logs and code context for an evidence-based diagnosis process that eliminates guesswork and pinpoints exact triggers.

The best way to debug runtime exceptions and compile errors is applying a no-assumptions rule that requires user-provided logs and codebase context to validate hypotheses and output explicit root-cause statements.

Systematically troubleshoot unit test failures by following a hypothesis-verification loop that analyzes logs and code context, expanding the information scope after three or more unresolved iterations.

Yes, you need to provide specific environment information and logs for log analysis and root-cause diagnosis, because the process enforces a strict no-assumptions rule requiring concrete evidence for all conclusions.

You should expand the information scope during issue diagnosis when a hypothesis-verification loop ends after three or more rounds without confirming a root cause, requiring broader codebase context research.