explain

To explain code functions in plain language, provide a file path or function name. The analysis identifies what the code does, why it exists, and potential pitfalls, delivering a structured summary with design considerations.

Understanding design rationale requires analyzing the file's context and structure. This plain-language explanation highlights key design decisions, trade-offs, and common mistakes to clarify why the code exists and how it operates.

Yes, you can request an explanation using a file path or function name. The context-aware analysis locates the relevant portion of the codebase and provides a concise, structured description of the targeted code.

Yes, plain-language code analysis includes potential pitfalls and handles edge cases. The explanation delivers structured design notes that highlight common mistakes and key trade-offs found within the specified code block.

Analyzing code without reading every line involves providing the function name or path. The analysis locates the relevant codebase context and outputs a structured explanation covering the code's purpose, design, and pitfalls.

You should provide a clear file path or function name to get a structured explanation. Optionally including broader context allows the analysis to accurately handle edge cases and deliver concise design notes.