Python Code Review
Systematic code review with actionable feedback organized by severity.
Process
Gather context
git diff --name-only main git diff main git log main..HEAD --onelineRun automated checks
ruff check --output-format=json <files> vulture --min-confidence=80 <files> mypy <files>Apply review checklists - see references below
Generate report with issues and fix plan
Severity Levels
| Level | Definition | Action |
|---|---|---|
| Critical | Security flaws, data loss, breaking changes | Blocks merge |
| High | Resource leaks, wrong layer, N+1 queries | Fix before merge |
| Moderate | Missing tests, complexity >10, swallowed exceptions | Should address |
| Low | Style beyond linter, minor refactoring | Optional |
Review Categories
Apply these checklists to changed files:
Architecture - Layer violations, dependency direction, god classes
- See references/architecture.md
Security - Injection, secrets, path traversal, deserialization
- See references/security.md
Quality - Complexity, error handling, performance
- See references/quality.md
Testing - Coverage, assertions, isolation, fixtures
- See references/testing.md
Documentation - Docstrings, README accuracy
- See references/documentation.md
Deployment - Dockerfile, Helm, migrations
- See references/deployment.md
Consistency - Code-docs sync, signature matches
- See references/consistency.md
Output Format
# Code Review Report
**Status**: PASS | NEEDS_WORK | BLOCKED
## Issues
| Severity | Count |
|----------|-------|
| Critical | N |
### [Category]
- [severity] file:line - description
- Fix: specific suggestion
## Fix Plan
1. [Issue] - [Action]
Principles
- Be specific: "Add try/except at line 42" not "improve error handling"
- Verify first: Check functions exist before suggesting them
- Focus on changes: Don't refactor untouched code
- Provide working examples