debugger-research-reasoning

Debugging decisions require analyzing error messages, stack traces, and code context to determine whether external research or internal code reasoning fits the problem. A decision-tree framework evaluates signals to recommend the correct action.

Triage error investigations and library behavior ambiguities by applying a decision framework that cross-references debugging patterns and how-to-research templates, balancing external lookups with code reasoning to prevent wasted time.

Use a debugging decision framework when facing platform differences, domain knowledge gaps, or library behavior ambiguities to avoid drift between research and code reasoning, ensuring actions align with the specific problem context.

Prevent over-research or over-reasoning during error investigations by using balance indicators and best practices that guide your debugging sessions, aligning actions with problem context to minimize wasted time and drift.

Debugging triage applies to domain knowledge gaps across codebases by evaluating error messages, stack traces, and code context, then specifying decisions and recommended actions for both research and reasoning steps.

Debugging decision processes require inputs like error messages, stack traces, and code context to evaluate the problem, producing outputs that specify decisions and recommended actions for research and reasoning steps.