python-code-review

Reviewing Python code changes before a pull request involves inspecting diffs for correctness bugs, design problems, and security risks. This Skill analyzes staged changes or branches to check type hints, pytest coverage, and security boundaries.

Yes, you can check staged Python diffs against ruff and pyright configurations. The review process reads project conventions from pyproject.toml to evaluate modern linting, typing, and structural quality.

Automating pytest coverage verification for new Python branch changes is best handled by analyzing the diff to ensure new behaviors have tests. This Skill flags missing test coverage while applying SOLID and DRY principles.

Yes, the Python code review process follows project specific conventions defined in CLAUDE.md and pyproject.toml. It evaluates function structure, resource handling, and logging based on these established project rules.

To catch missing test coverage and injection risks in Python diffs before commit, run a structured branch review. This process verifies new behavior has tests and flags security concerns like exposed secrets or injection vulnerabilities.

You need a dedicated Python code review for your pull request when you want to catch contract violations and boundary issues early. It provides a structured report with prioritized findings and suggested fixes before merging.