explain

To understand code without modifying it, use a read-only explanation approach that describes functions and flows while pointing out key decisions. This method outlines how the code operates step-by-step, providing references to file and line numbers to aid navigation during reviews.

The best way to explain code flow during code reviews or onboarding is to apply a read-only analysis that outlines step-by-step reasoning. This highlights key decisions and provides direct file and line-number citations, enabling quick comprehension of new codebases without making changes.

Yes, you can analyze code across different languages for debugging sessions. The read-only explanation process applies universally across languages and projects, detailing how functions operate and citing specific line numbers to help you trace logic without altering the codebase.

To get a step-by-step explanation of a function's logic, target the specific code for read-only analysis. The process describes the function's operations, points out key decisions within the flow, and provides line-number references for easy navigation through the logic.

No, read-only code explanation does not require write access. It satisfies requirements for read access to the target files and contextual references, ensuring the codebase remains completely unmodified while you review or debug the logic.