코딩 · 개발원문 · prompts.chat

코드 파일 분석 및 언어 변환

임의의 코드 파일을 분석하고 Python 코드를 Java, .NET, PHP 등 다른 프로그래밍 언어로 변환합니다.

원제 · Analyze any code file

추천 툴: 공통형식 기준 추천

프롬프트 원문

Analyze the provided Python file like a senior/veteran Python developer who is seeing it for the first time.

Explain it in simple, easy-to-understand language while preserving the technical context.

Cover:

1. **Purpose** — what this file does and why it exists.
2. **Flow** — explain the main execution flow from entry point to completion.
3. **Functions/Classes** — explain the important functions/classes, their inputs, outputs, and responsibilities.
4. **Dependencies** — explain important imports, external APIs, files, databases, services, or modules it interacts with.
5. **Data Flow** — explain how important data moves, changes, and is passed between functions/classes.
6. **Conditions & Loops** — explain important `if/else`, loops, retries, exceptions, and decision points.
7. **Side Effects** — identify file writes, database/API calls, state changes, external operations, etc.
8. **Risks & Issues** — identify bugs, edge cases, unnecessary complexity, coupling, or maintainability concerns.
9. **Summary** — give a short step-by-step flow that a developer can remember easily.

Focus on understanding the **actual code and execution flow**, not merely describing each line. Do not invent behavior that cannot be determined from the file. If something depends on another file/module that is not provided, clearly mention it.

Keep the explanation structured, concise, and easy to follow. Prioritize important logic over trivial syntax.

‹ 라이브러리로

Analyze the provided Python file like a senior/veteran Python developer who is seeing it for the first time. Explain it in simple, easy-to-understand language while preserving the technical context. Cover: 1. **Purpose** — what this file does and why it exists. 2. **Flow** — explain the main execution flow from entry point to completion. 3. **Functions/Classes** — explain the important functions/classes, their inputs, outputs, and responsibilities. 4. **Dependencies** — explain important imports, external APIs, files, databases, services, or modules it interacts with. 5. **Data Flow** — explain how important data moves, changes, and is passed between functions/classes. 6. **Conditions & Loops** — explain important `if/else`, loops, retries, exceptions, and decision points. 7. **Side Effects** — identify file writes, database/API calls, state changes, external operations, etc. 8. **Risks & Issues** — identify bugs, edge cases, unnecessary complexity, coupling, or maintainability concerns. 9. **Summary** — give a short step-by-step flow that a developer can remember easily. Focus on understanding the **actual code and execution flow**, not merely describing each line. Do not invent behavior that cannot be determined from the file. If something depends on another file/module that is not provided, clearly mention it. Keep the explanation structured, concise, and easy to follow. Prioritize important logic over trivial syntax.