Python Code Review Patterns

Stack-specific rules loaded by dh:code-reviewer when pyproject.toml or *.py files are detected.

Type Annotations

• All public function boundaries must have type annotations — parameters and return type
• Any is only acceptable with an inline comment explaining why a specific type cannot be used
• TypedDict is required for dicts that cross module boundaries; plain dict[str, ...] is only acceptable within a single function
• Optional[X] is legacy — use X | None (Python 3.10+ union syntax)
• Union[X, Y] is legacy — use X | Y
• Return type None must be explicit on functions that have no return value but have side effects
• Protocol classes are preferred over ABC for structural typing

Ruff Compliance