explain

To explain complex code architecture, you must read all relevant files completely and trace the end-to-end data flow from input to output. This process converts intricate logic into an objective, step-by-step walkthrough that clarifies dependencies and processing sequences for new developers.

The best way to document system workflows without guessing intent is to ground your explanation strictly in observable code. Summarize the functional behavior in 1-3 sentences, then provide an input-to-output processing walkthrough based exclusively on what the source actually does.

To identify integration risks and edge cases during a code review, analyze the explicit dependencies and trace the data flow across components. Highlighting points of complexity and integration risks requires complete reading of the relevant files to ensure no potential failure point is missed.

Yes, you can use automated explanation techniques for incident follow-up by performing explicit dependency identification and end-to-end data-flow tracing. This approach highlights observed edge cases and complexity points, providing objective reasoning grounded in the provided source.

Yes, explaining architecture requires the complete reading of relevant files to ensure correct reasoning and traceable details. Without reading the entire source, you risk missing explicit dependencies, edge cases, and integration risks, which leads to guessing the system's design intent.

You should avoid using automated code explanation when the relevant source files are incomplete or inaccessible. Since this process prohibits inventing intent and requires grounding design justification in observable code, missing files will result in an inaccurate risk assessment and flawed data flow tracing.