omk-python-typing

Enforce Python type hints by applying static analysis with pyright and ruff to standardize public APIs, prefer pathlib Path, and avoid mutable defaults. This generates a fix plan for typing issues, runtime risks, and test gaps.

Align static analysis with pytest by enforcing typed development standards that separate IO from business logic. This identifies test gaps and runtime risks, producing a comprehensive typing and testing fix plan for your repository.

Set up a new Python repository by applying standards for type hints and structured modeling via dataclasses or Pydantic. This workflow uses ruff, pyright, pytest, and uv to catch issues early and maintain codebase quality.

You can review pull requests by checking for type hints on public functions and proper pathlib Path usage. The review separates IO from business logic and generates a fix plan for typing issues and runtime risks.

Avoid mutable defaults and separate IO from business logic to prevent type-related defects and maintainability drift. This practice ensures runtime safety and aligns your code with strict static analysis standards.