omk-quality-gate

What problem does it solve?

It prevents teams from claiming an implementation is complete when linting, type checking, tests, builds, or regression checks were skipped or failed silently.

Core Features & Use Cases

• Coordinated quality checks: Runs or explicitly marks unavailable the standard sequence of lint, typecheck, tests, build, and regression-style acceptance.
• Transparent completion evidence: Produces an explicit report listing changed files, which commands were run, what passed or failed, what was not run, and why.
• Risk-aware sign-off: Assesses regression risk and ensures the final diff is reviewed before acceptance.

Quick Start

Run the omk-quality-gate workflow after updating code, then report changed files, the commands executed, and the passing, failing, and skipped results in the required text format.