Coding
Python Code Performance & Quality Enhancer
- Tested with:
- GPT-4o
- Effectiveness:
- 85/100
- Prompt archive
English version
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}Fill in and run
This prompt has 4 blanks. Fill them in and we will assemble the finished prompt for you.
4 still empty
Finished 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}- Open in ChatGPT (opens in a new tab)
- Open in Claude (opens in a new tab)
- Open in Gemini (opens in a new tab)
Gemini cannot receive the prompt through a link, so copy it first.
- Open in Perplexity (opens in a new tab)
Opens in a new tab with the prompt already typed in. You may need to be signed in.
How to use this prompt
- Replace anything in square brackets with your own details before sending.
- Results differ between models. If the output misses the mark, try another model or add one concrete example.
- Keep the prompt in one message. Splitting it across turns weakens the instructions.