review-python

Python code review is automated by scanning .py file changes for type annotation, linting, and import order violations against team conventions. It performs seven structured checks covering typing, casts, imports, and documentation, returning actionable findings with evidence and suggested fixes.

Static analysis for Python coding standards is the automated process of checking .py files for type safety, import order, and documentation adherence without executing the code. It identifies structural deviations from team conventions to ensure consistent, high-quality code during reviews.

Check Python type annotations and imports by running comprehensive review passes that enforce type safety, cast usage, and import order. The analysis targets .py files, identifies deviations from team conventions, and provides evidence with suggested fixes for each issue found.

Yes, team coding standards can be enforced across the repository by identifying and reporting Python code that violates conventions in any .py file. It enforces checks for type safety, style, import order, and documentation, returning findings with evidence and suggested fixes.

Yes, Python static analysis provides suggested fixes for linting and style violations. Each identified issue includes actionable evidence and remediation steps, accelerating the process of resolving type safety, import order, and documentation deviations during code reviews.

The limitations of automated Python code review include its strict focus on .py files and its scope limited to type safety, linting, import order, and documentation checks. It enforces team conventions but may not catch complex runtime logic errors or architectural flaws outside these specific categories.