prompt GP ChatGPT

Python Code Performance & Quality Enhancer — ChatGPT and Claude.ai

A review prompt for Python: adds docstrings, fixes PEP8, lists performance issues with Big O impact, and returns the full rewritten file.

Open on GitHub

What Python Code Performance & Quality Enhancer does

The prompt walks the model through five steps. First a documentation audit: docstrings in Google or NumPy style, comment review, type hints. Then PEP8 — naming, indentation, line length, import order — with a one-line reason for every fix.

Step three is a performance table: area, issue, suggested fix, severity, complexity impact, including Big O changes. Missing error handling gets flagged too when the code does something risky. Logic and output stay untouched unless there is a clear bug.

After that comes the complete rewritten code with no placeholders, and a before/after card covering docs, PEP8, performance and complexity. You paste your snippet straight into the prompt, so a large file has to be split into chunks.

What it helps with

add docstrings to an undocumented function
clear PEP8 violations and unused imports
spot performance bottlenecks and Big O shifts
get the whole file rewritten, not a fragment
see every change with a short justification

Example prompts for the agent

Review this Python code step by step: docstrings, PEP8, performance, then the full version. ${paste_your_code_here}
Run my script through this and show the performance issue table with Big O
Rewrite the module: type hints, import order, error handling. Keep the logic as is

How to install Python Code Performance & Quality Enhancer

How to use

Paste the text at the start of a chat or into project instructions

Manually: put the files in place

.claude/commands/prompts.csv.md

Questions about Python Code Performance & Quality Enhancer

How to install Python Code Performance & Quality Enhancer in ChatGPT?

There is nothing to install: copy the prompt text into the chat as your first message and replace ${paste_your_code_here} with your code.

What does Python Code Performance & Quality Enhancer do?

It runs your code through five steps: documentation, PEP8, a performance plan, the full rewritten code, and a summary table of changes.

Does the prompt change the logic of my code?

No, unless it is clearly a bug. The instructions say not to alter logic or output.

Source text

prompts.csv · CC0-1.0

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}

python-patterns affaan-m Tells the agent how to write and review Python: idioms, type hints, exception handling, context managers. CX Codex +1 5,500installs python-performance-optimization Seth Hobson This skill profiles Python code to locate CPU and memory bottlenecks. Use it when an application responds slowly or consumes too many resources. CX Codex 35,675installs

From the same set77

The whole set →