explain-code

To explain software architecture in plain language, provide the specific file paths, function names, or code snippets. The system processes these inputs to detail design patterns and step-by-step logic without needing prior project context.

Understanding an unfamiliar codebase for onboarding involves analyzing specific modules like an authentication function. Providing the file path allows the system to break down the code's purpose, functionality, and system placement for new developers.

Yes, you can use code snippets to identify design patterns. The system accepts snippets directly, analyzes the implementation logic, and suggests related code to facilitate deeper understanding and knowledge transfer.

Code explanation works by taking the provided function name and locating its implementation. It then outlines the step-by-step logic, identifies any architectural choices used, and delivers a comprehensive plain-language summary.

Knowledge transfer for software development does not strictly require full file paths. You can provide class names, function names, or direct code snippets to receive an explanation of the functionality and design decisions.

You do not need to provide prior context when explaining code functionality. The system demystifies complex codebases by deriving the purpose, architecture, and design decisions directly from the submitted code snippets or file paths.