What problem does it solve? When a commit or push is blocked by a git hook or Claude hook in the kami-kakushi repo, developers need to know which escape flag (if any) is legitimate, what each SKIP_/KAMI_ variable actually does, and how to add new flags without widening the bypass surface. This Skill is the single reference catalog for every flag, env var, vite define, URL boot param, and balance-cockpit lever, each anchored to its enforcing file:line. ## Core Features & Use Cases - Escape flag catalog: Tables covering commit/push escapes (SKIP_VERIFY, SKIP_JOURNAL, SKIP_QUEUE, SKIP_ATTRIB), Claude-hook escapes (SKIP_SWEEPGUARD, SKIP_DEVGUARD, KAMI_ALLOW_MULTI_DEV), script env vars (VERIFY_FULL, UPDATE_MAP_GOLDEN, SHIP_DEV_TOOLS, QA_URL), vite defines (DEV_TOOLS, VERSION), and URL boot params (?dev, ?fixture, ?bal.<path>, ?story-<bundle>). - Ground rules and hard blocks: Documents which combinations are hard-blocked (e.g. SKIP_VERIFY=1 with git push) and which destructive git ops have no escape at all. - Add-a-flag checklist: Per-class procedures for safely introducing new gates, hook escapes, env vars, defines, URL params, and cockpit levers. - Re-derive greps: Ready-to-run grep commands to regenerate every table when the catalog drifts from the code. - Use Case: A commit is blocked by the sweep guard on git add -A; consult this Skill to learn that SKIP_SWEEPGUARD=1 is the escape, that every use is auto-logged to the sweepguard ledger, and what the legitimate case is. ## Quick Start Ask the assistant to load the kami-config-and-flags skill and explain what SKIP_CODE_VERIFY does and when it is legitimate to use.
