Проверка готовности кода к слиянию

★ 8.5 · productivity

merge-readiness is a Claude Code skill that acts as a post-task explainability gate: it generates a human-readable report on a change and then quizzes the team to verify they can explain why the change exists, what changed, what tradeoffs were made, and what risks were considered before merge approval is requested. Three depth profiles are supported — quick (correctness threshold ≥ 0.70, up to 3 MCQs), standard (≥ 0.80, up to 5 MCQs), and deep (≥ 0.90, up to 8 MCQs) — covering five required dimensions: why, change, tradeoff, risk, and team. Questions are presented one per round via AskUserQuestion; scoring is handled objectively by the runtime hook (`mcq.ts`), not by AI heuristics. Session state persists to `.omc/state/merge-readiness-state.json` for resume safety. Passing the gate never replaces tests, code review, or maintainer approval — it only confirms the team can explain the change.