kerbylisted

Load, install, reload, check status of, uninstall, prepare, or audit an existing repo for the kerby guardrails system. Invoke ONLY when the user explicitly mentions "kerby", "/kerby", or asks to load/unload/install/uninstall/check/ list-or-create-rulebooks/prepare (onboard an existing repo into) or audit-a-repo-against the kerby guardrails. Do NOT invoke on general coding tasks (fixing bugs, implementing features, refactoring) — kerby is a meta-system that itself governs how those tasks are done; `audit` checks a repo's conformance to the rules, it is NOT a general bug/security review. Engine sub-commands via the args parameter: `load` (default), `unload`, `reload`, `status`, `install`, `uninstall`, `rulebooks [list]|create`, `commands`, `check-updates`; loaded rulebooks add their own commands (e.g. the bundled `swe` rulebook provides `prepare` and `audit`).
sorawit-w/kerby · ★ 0 · Code & Development · score 72

Install: claude install-skill sorawit-w/kerby

# kerby — session loader This skill loads the `kerby` guardrails into the current session and provides per-project install utilities. **The skill does not contain the rules themselves** — those live in **self-contained rulebook folders** under `./rulebooks/` (each with its own manifest, prose bodies, references, workflows, and hooks), while `./resources/` holds only engine machinery (the validator, the SessionStart state hooks, state templates, engine references). ## Locating the bundled rule content Resolve the **install root** via the first method that succeeds: 1. **Glob discovery (preferred).** Use the `Glob` tool with pattern `**/skills/kerby/SKILL.md`; the install root is that file's parent directory. Common install locations are `~/.claude/skills/kerby` (global) or `<project>/.claude/skills/kerby` (project-local). Use the first match that exists. Never glob for BOOTSTRAP.md — the engine anchors on SKILL.md; rulebook bodies (including external clones under `.kerby/rulebooks/`) are resolved from the install root, and a BOOTSTRAP glob could match any rulebook's copy. 2. **`KERBY_DIR` env var.** If set, the install root is `${KERBY_DIR}`. 3. **Ask the user.** If both fail: "Where is your kerby install? (Could not auto-locate BOOTSTRAP.md.)" From the install root: rulebooks live at `<install-root>/rulebooks/<id>/`, engine machinery at `<install-root>/resources/`. The locator finds the *install*; **what to load comes from rulebook manifests**, below. --- ## Rulebooks,