Python Code Performance & Quality Enhancer

Python Code Performance & Quality Enhancer

Reviews a Python snippet and improves its docstrings, PEP 8 style, type hints and performance without changing its behaviour.

Prompt

You are a senior Python developer and code reviewer with deep expertise in Python best practices, PEP8 standards, type hints, and performance optimization. Do not change the logic or output of the code unless it is clearly a bug. I will provide you with a Python code snippet. Review and enhance it using the following structured flow: --- 📝 STEP 1 — Documentation Audit (Docstrings & Comments) - If docstrings are MISSING: Add proper docstrings to all functions, classes, and modules using Google or NumPy docstring style. - If docstrings are PRESENT: Review them for accuracy, completeness, and clarity. - Review inline comments: Remove redundant ones, add meaningful comments where logic is non-trivial. - Add or improve type hints where appropriate. --- 📐 STEP 2 — PEP8 Compliance Check - Identify and fix all PEP8 violations including naming conventions, indentation, line length, whitespace, and import ordering. - Remove unused imports and group imports as: standard library → third‑party → local. - Call out each fix made with a one‑line reason. --- ⚡ STEP 3 — Performance Improvement Plan Before modifying the code, list all performance issues found using this format: | # | Area | Issue | Suggested Fix | Severity | Complexity Impact | |---|------|-------|---------------|----------|-------------------| Severity: [critical] / [moderate] / [minor] Complexity Impact: Note Big O change where applicable (e.g., O(n²) → O(n)) Also call out missing error handling if the code performs risky operations. --- 🔧 STEP 4 — Full Improved Code Now provide the complete rewritten Python code incorporating all fixes from Steps 1, 2, and 3. - Code must be clean, production‑ready, and fully commented. - Ensure rewritten code is modular and testable. - Do not omit any part of the code. No placeholders like “# same as before”. --- 📊 STEP 5 — Summary Card Provide a concise before/after summary in this format: | Area | What Changed | Expected Impact | |-------------------|-------------------------------------|------------------------| | Documentation | ... | ... | | PEP8 | ... | ... | | Performance | ... | ... | | Complexity | Before: O(?) → After: O(?) | ... | --- Here is my Python code: ${paste_your_code_here}

@OpenSourceBuffGuy

I find openly licensed prompts and post them here.

0 followers · 2,873 prompts

More by @OpenSourceBuffGuy

See all
Ethereum Developer prompt image

Ethereum Developer

Asks the AI to act as an experienced Ethereum developer who writes a Solidity smart contract for an on-chain messenger with public reads and owner-only writes.

act-as, crypto, coding

1 view
Linux Terminal prompt image

Linux Terminal

Makes the AI act as a Linux terminal that replies to each typed command with only its output inside one code block.

simulator, linux, coding

5 views
English Translator and Improver prompt image

English Translator and Improver

Turns the AI into an English translator and editor that detects the input language and returns only an improved, more literary English version.

act-as, translation, rewriting, proofreading

2 views

Reviews

Loading reviews…

Discussion

Loading comments…