← ClaudeAtlas

notabene-setuplisted

Install, configure, OR reconfigure notabene (the docs review tool) and start its review server — for a user who drives everything through the agent, on any stack (Rust/Python/Go/JS, no toolchain needed). Use to GET STARTED / LAUNCH: "set up notabene", "install notabene", "set up docs review/commenting", "start the review server", "open the review UI", "I want to leave comments on / review my docs", "get notabene running". Use to RECONFIGURE (a notabene.config.mjs already exists): "add/remove/rename a docs folder", "move the store", "switch review to approve/validation mode", "change notabene's port", "rename the site", "change the language", "add a verify step", "expose it on the LAN". This skill does NOT act on existing comments — processing review feedback is the `notabene` skill, which it hands off to once the server is up. Writes/edits notabene.config.mjs (shown first), creates the store, launches the server. Never commits; never exposes the LAN without an explicit request.
z29k/notabene · ★ 5 · AI & Automation · score 72
Install: claude install-skill z29k/notabene
# notabene setup (install · reconfigure · run) Get a user from nothing (or from a config they want changed) to an open review server, **with zero npm/build commands typed by hand**, on any repo. The renderer is fetched and run **through `npx`** — nothing is installed into the user's repo; only **data** lives there (`notabene.config.mjs` + the `.notabene/` store + their docs). Everything routes on **`doctor`** (read-only state) — you encode **no** defaults yourself. This skill only sets things up; **processing comments is the `notabene` skill** (hand off at the end). ## The forwarder — how you call the tool Never call `npx notabene` (unscoped — that package does not exist on npm) and never hardcode a version. Always go through the plugin forwarder, which pins the right renderer: ```bash node "${CLAUDE_PLUGIN_ROOT}/bin/nb.mjs" <subcommand> --root <repo-root> [flags…] ``` `<repo-root>` = the current project directory (the repo whose docs you're reviewing). Use its absolute path. `nb.mjs` forwards to `npx -y --prefer-offline @z29k/notabene@<pinned>`. ## Golden rules (no exceptions) - **Never commit / push / rewrite history** without an explicit request. Tell the user to commit the config + `.notabene/` store; don't do it for them. (Offering `git init` on a non-repo is fine — that's not a commit.) - **Never expose the LAN** (`host: true` / `--host`) unless the user explicitly asks. It's loopback-only by default; keep it that way. - **Never `rm -rf` the store** or reg