refine

Automating pre-commit code review involves running a coordinated seven-pass quality gate over changed code, executing passes like comment, style, fix-types, and interface sequentially to verify quality before committing.

A multi-pass code quality workflow coordinates individual checks such as comment, lerp, style, fix-types, interface, test-invariants, and exemplar-audit. Each pass reads its own skill file for a full checklist, enabling deterministic and repeatable quality verification.

Yes, you can target individual passes by name to run checks like fix-types or test-invariants independently, or execute all seven passes in sequence to comprehensively polish changed code.

You verify code invariants within an automated testing workflow by running the test-invariants pass, which acts as one step in a seven-pass quality gate to ensure deterministic code quality verification before final commits.

No, this quality gate workflow operates without external dependencies. It uses independent skill files to keep checks modular and evolvable, enabling a centralized and repeatable quality-check process directly over changed code.

Use a seven-pass quality gate when you need to orchestrate multiple checks—like interface consistency, type fixing, and exemplar audits—beyond standard linting, providing a centralized and repeatable workflow to polish code before commits.