clarify

Debugging unexpected code behavior requires gathering evidence by reading relevant code, checking configuration, and reviewing documentation. This approach verifies your intent, explains actual behavior, and determines whether a real issue exists before proposing a fix.

Analyzing code and configuration to resolve confusion involves investigating the actual codebase, checking settings, and reviewing documentation. This evidence-based process categorizes the confusion source—such as memory gaps, project mixing, or outdated mental models—to provide a grounded explanation.

Evidence-based explanations for code not working as documented are generated by cross-referencing actual code behavior with available documentation. This process identifies whether the issue stems from documentation gaps, configuration issues, or a real bug in the code.

Yes, it specifically identifies confusion signals like an outdated mental model or project mixing. By verifying your original intent against the actual codebase and configuration, it provides a grounded explanation that corrects your understanding of the project.

When code analysis detects a real bug or design flaw, you can enter plan mode to design and implement a fix. This mode provides evidence-based reasoning and a clear, actionable next-step plan to resolve the identified issue.

Evidence-based code analysis for resolving confusion is limited by the availability and accuracy of existing code, configuration, and documentation. Without accessible evidence, the tool cannot provide grounded explanations or determine if a real issue exists.