python-code-review

# Python Code Review Expert

## ⚠️ MANDATORY COMPLIANCE ⚠️

**CRITICAL**: The 5-step workflow outlined in this document MUST be followed in exact order for EVERY code review. Skipping steps or deviating from the procedure will result in incomplete and unreliable reviews. This is non-negotiable.

## File Structure

- **SKILL.md** (this file): Main instructions and MANDATORY workflow
- **examples.md**: Review scenarios with before/after examples
- **../../context/python/**: Framework patterns and detection logic
  - `context_detection.md`, `common_issues.md`, `{framework}_patterns.md`
- **../../context/security/**: Security guidelines and OWASP references
  - `security_guidelines.md`, `owasp_python.md`
- **../../memory/skills/python-code-review/**: Project-specific memory storage
  - `{project-name}/`: Per-project learned patterns and context
- **templates/**: `report_template.md`, `inline_comment_template.md`

## Review Focus Areas

Deep reviews evaluate 8 critical dimensions **in the changed code**:

1. **Production Quality**: Correctness, edge cases, error recovery, resilience
2. **Deep Bugs**: Race conditions, memory leaks, resource exhaustion, subtle logic errors
3. **Security**: Injection flaws, auth bypasses, insecure deserialization, data exposure
4. **Performance**: Algorithmic complexity, N+1 queries, memory inefficiency, I/O blocking
5. **Architecture**: Tight coupling, missing abstractions, SOLID violations, circular deps
6. **Reliability**: Transaction safety, error handling, resource leaks, idempotency
7. **Scalability**: Concurrency issues, connection pooling, pagination, unbounded consumption
8. **Testing**: Missing critical tests, inadequate edge case coverage

**Note**: Focus on substantive issues requiring human judgment, not style/formatting details. Reviews are performed on changed code only, using the `get-git-diff` skill to identify modifications.

---

## MANDATORY WORKFLOW (MUST FOLLOW EXACTLY)

### ⚠️ STEP 1: Identify Changed Files via Git Di