# Python Review

> Python review checklist — what to check in Python code, by severity. A reference for writing and reviewing it; in a workflow run the review step records each problem as a finding and the engine decides what blocks.

- Skill: `keyvaluesoftwaresystems/python-review` (Agent Skill)
- Install (CLI): `npx get-skill add keyvaluesoftwaresystems/python-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/keyvaluesoftwaresystems/python-review/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: keyvaluesoftwaresystems (https://skillmd.com/u/keyvaluesoftwaresystems)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/keyvaluesoftwaresystems/python-review

---


# Python review checklist

Use this when writing or reviewing Python code. The severities say how serious a problem is; they are guidance for a finding's severity, not a verdict.

## Review Priorities

### CRITICAL — Security
- **SQL Injection**: f-strings in queries — use parameterized queries
- **Command Injection**: unvalidated input in shell commands — use subprocess with list args
- **Path Traversal**: user-controlled paths — validate with normpath, reject `..`
- **Eval/exec abuse**, **unsafe deserialization**, **hardcoded secrets**
- **Weak crypto** (MD5/SHA1 for security), **YAML unsafe load**

### CRITICAL — Error Handling
- **Bare except**: `except: pass` — catch specific exceptions
- **Swallowed exceptions**: silent failures — log and handle
- **Missing context managers**: manual file/resource management — use `with`

### HIGH — Type Hints
- Public functions without type annotations
- Using `Any` when specific types are possible
- Missing `Optional` for nullable parameters

### HIGH — Pythonic Patterns
- Use list comprehensions over C-style loops
- Use `isinstance()` not `type() ==`
- Use `Enum` not magic numbers
- Use `"".join()` not string concatenation in loops
- **Mutable default arguments**: `def f(x=[])` — use `def f(x=None)`

### HIGH — Code Quality
- Functions > 50 lines, > 5 parameters (use dataclass)
- Deep nesting (> 4 levels)
- Duplicate code patterns
- Magic numbers without named constants

### HIGH — Concurrency
- Shared state without locks — use `threading.Lock`
- Mixing sync/async incorrectly
- N+1 queries in loops — batch query

### MEDIUM — Best Practices
- PEP 8: import order, naming, spacing
- Missing docstrings on public functions
- `print()` instead of `logging`
- `from module import *` — namespace pollution
- `value == None` — use `value is None`
- Shadowing builtins (`list`, `dict`, `str`)

## Diagnostic Commands

```bash
mypy .                                     # Type checking
ruff check .                               # Fast linting
black --check .                            # Format check
bandit -r .                                # Security scan
pytest --cov=app --cov-report=term-missing # Test coverage
```

## Framework Checks

- **Django**: `select_related`/`prefetch_related` for N+1, `atomic()` for multi-step, migrations
- **FastAPI**: CORS config, Pydantic validation, response models, no blocking in async
- **Flask**: Proper error handlers, CSRF protection

## Reference

For detailed Python patterns, security examples, and code samples, see skill: `python-patterns`.

---

Review with the mindset: "Would this code pass review at a top Python shop or open-source project?"

