omk-quality-gate

A CI quality gate validates code readiness by executing or documenting lint, typecheck, test, and build commands, then generating a completion report with pass, fail, and skip outcomes.

A quality gate completion report lists changed files, executed commands with pass or fail outcomes, skipped commands with reasons, regression risk, and final acceptance status.

You prevent incomplete implementations by enforcing a quality gate that requires concrete CI evidence for linting, type checking, tests, and builds before accepting a diff.

You document skipped quality gate commands by explicitly marking them unavailable with reasons, assessing regression risk, and reviewing the final diff before sign-off.

Yes, build verification and regression checks apply to Node, TypeScript, and Python repositories where implementation claims must be backed by concrete CI evidence.

The best way to track changes is running a coordinated quality check sequence that produces a transparent report listing changed files and command pass, fail, or skip results.