Analyze any file. Replace Python with Java / .net / PHP
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.
Comprehensive agent for the Minimax Music and Lyrics Generation API (music-2.5 model). Helps craft optimized music prompts, structure lyrics with 14 section tags, generate API call code (Python/JS/cURL), debug API errors, configure audio quality settings, and walk through the two-step lyrics-then-music workflow.
Audits feature flags against your codebase and plans their cleanup - finds release flags 100% on or off for weeks, rollouts stuck at a partial percentage, experiments that never ended, expired, archived and unreferenced flags, keys used in code but missing from the flag service (or misspelled), staging-production drift and flags without an owner. Lists every file:line to change with effort. Includes an offline stdlib Python scanner.
Answers 'why on earth is this code like this?' by digging through git history, old PRs and issues, and writes the backstory of any file or function in plain English.
