What problem does it solve? When pnpm run verify (or a pre-commit, pre-push, or CI run) goes RED in the kami-kakushi repository, developers need to know what that specific gate checks, why it exists, and the sanctioned fix — without guessing or bypassing quality gates. ## Core Features & Use Cases - Gate-by-gate fix book: Covers all 21 roster gates (tsgo, oxlint, oxfmt, vitest, gen-docs, fixtures, gen-narrative, gen-prd-regions, checkpoint, verify-content, verify-prd, verify-changelog, md-links, milestone-integrity, pacing, playcheck, doc-budgets, inbox-ledger, review-link, deferred-work, human-todo) with the exact regen or repair command for each. - Lane mechanics guidance: Explains SKIP_CODE_VERIFY / SKIP_DOCS_VERIFY / VERIFY_FULL scoping, the 8-second commit budget, and which pre-commit checks are NOT roster gates. - Meta-rules enforcement: Codifies invariants like "regen, don't hand-edit", "never widen a threshold to go green", and "don't fight someone else's red" in a shared working tree. - Use Case: A commit is blocked because gen-docs reports t0-content.md is stale; the skill directs you to run pnpm run gen:docs and commit the regenerated output with the triggering change. ## Quick Start Ask the assistant to diagnose why the verify gate went RED and give the sanctioned fix for the failing gate.
