quality-gate

Perform a three-phase post-build quality review to identify structural issues, AI prompt anti-patterns, and APOSD design concerns. It targets files changed since the build base, skipping generated, lock, migration, and test fixtures, and outputs a structured report with recommended fixes.

A three-phase quality gate enforces structural quality checks like code reuse and SOLID principles in Phase 1, removes AI anti-patterns in Phase 2, and performs APOSD design checks in Phase 3, generating a comprehensive report with actionable fixes.

Scope a static analysis review by targeting files changed since the build base or by specifying a user-scope path. This focuses the design review on relevant code while automatically skipping generated, lock, migration, and test fixture files.

Yes, the quality gate review skips generated, lock, migration, and test fixture files. It exclusively targets changed files or a user-specified scope path to ensure the structural and design checks focus on relevant source code.

Yes, you can use this quality gate for APOSD design reviews and SOLID principle checks. Phase 1 enforces structural quality including SOLID and complexity, while Phase 3 specifically handles APOSD design concerns to output recommended fixes.

The best way to remove AI anti-patterns is running Phase 2 of the post-build quality gate. It detects and deslops AI prompt anti-patterns in changed files, providing a comprehensive report with actionable fixes and a rerun-ready workflow.