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.
Lints a DNS zone file or a provider's CSV record export before it breaks web or mail - CNAME at the apex or next to other records, MX/NS pointing at a CNAME or IP, missing trailing dots, missing or duplicate SPF, +all/?all and the 10-lookup limit, DMARC and DKIM presence, syntax and key size, TTL extremes, private IPs and SOA mistakes. Returns corrected records. Includes an offline stdlib Python linter with --self-test.
Checks a Markdown docs folder for links that break readers - relative links to missing or renamed files, anchors that match no heading, duplicate heading anchors, file-name case that only works on macOS, local absolute paths, reference-style links with missing, unused or duplicate definitions, images without alt text and bare URLs. Works offline and lists external URLs to check separately. Includes a stdlib Python checker with --self-test.
