validate-and-fix

You can automate running tests and auto-fixing issues by executing a validation pipeline that handles unit, integration, and verify checks. It automatically resolves trivial failures like black formatting and unused imports, rerunning validations until tests pass or a real failure occurs.

The best way to run make-based linting and formatting checks is using an automated validation workflow. It applies ruff-fixable lint error corrections and formatting rules, enforcing guardrails by limiting auto-fix cycles to avoid infinite loops and reporting real failures when they occur.

Yes, the validation pipeline supports pytest unit and integration tests within a single workflow. It runs these checks alongside verification validations, applying automated fixes to trivial issues and rerunning the suite until the codebase stabilizes or a genuine failure is encountered.

Automated code fixing stops before resolving all test failures because it enforces guardrails with a defined limit on auto-fix cycles. This prevents infinite loops on unresolvable errors, ensuring the pipeline clearly reports real failures instead of repeatedly attempting trivial formatting or lint fixes.

Yes, you can use this validation workflow to verify changes before pushing to CI. It runs the project validation pipeline, auto-fixes trivial issues like formatting and unused imports, and ensures unit, integration, and verification checks pass, stabilizing your codebase prior to integration.