code-change-verification

To run formatting, linting, type checking, and tests for Python code changes, execute the verification script from the repository root. This automates the full code quality verification stack to validate runtime code modifications before merging.

A Make-based workflow for Python code verification uses Makefile targets like make format, make lint, make typecheck, and make tests to enforce code quality. It automates formatting, linting, type checking, and test execution for code changes.

Yes, you need git and make installed to automate Python code quality checks using this verification stack. The skill relies on Make-based workflows to execute targets for formatting, linting, type checking, and tests.

You should run the full code quality verification stack when you modify core library code, tests, or build configurations. This ensures runtime code changes and test behavior are validated by formatting, linting, type checking, and passing tests.

No, this verification stack requires a Make-based workflow with specific targets. It applies to Python repositories that have make format, make lint, make typecheck, and make tests configured to enforce code quality.