run-linters

Automate Python code quality checks before committing by invoking a unified linting process that runs formatting, style, and type-checking tools. This validates your codebase locally to ensure adherence to safety standards before staging changes.

The best way to run multiple Python linters in a CI/CD pipeline is using an automated execution skill that sequentially processes Black, flake8, mypy, and pyright. This prevents CI failures by validating code quality and compliance before deployment.

Yes, you need the uv environment to run these automated linting tools. The unified linting process explicitly requires the uv environment to execute Black, flake8, mypy, and pyright for maintaining clean and error-free codebases.

Yes, you can use this automated linting skill for pre-commit validation. It ensures code is clean and compliant by automatically verifying formatting, style, and type errors before you stage code for commits or trigger CI pipelines.

Automated Python type checking uses both mypy and pyright to provide comprehensive static analysis coverage. Running both tools ensures stricter adherence to style and safety standards by catching different categories of type errors in your codebase.

You should not use automated linting when your Python project lacks a uv environment setup or when immediate deployment is required without pre-commit validation. It is designed for ensuring compliance in CI/CD pipelines and local development, not for bypassing quality checks.