init

livewiki init command

The livewiki init command is the CLI entry point that provisions a repository's livewiki directories, indexes the source tree, and (optionally) drives the full LLM documentation pipeline.

When to use this page

• Wire the init subcommand into a Commander program and understand the option surface it accepts.
• Format the human-readable output of an init run, including skip notices and batch summaries.
• Diagnose exit-code and skip-behaviour decisions that differ between --json, --batch, and plan-only runs.

How it fits

packages/cli/src/commands/init.ts is a thin CLI adapter that lives inside the packages/cli/ wrapper. It registers the init subcommand on the top-level Commander program and delegates the actual work to runInit from @livewiki/core/init. The file also owns the human-readable formatter (formatHuman) that prints the result when the user did not request JSON output, and it normalises Commander's boolean flags (notably --no-refine) into the shape that runInit expects. Downstream, runInit decides which plan files, hub pages, and batch results come back; this file only shapes the call and the output.

Diagram

%% livewiki/diagrams/commands-init.mmd

Command registration

registerInit is the single registration function exported by this file. It attaches the init subcommand to the supplied program and wires the flag parser that the rest of the file relies on.

export function registerInit(program: Command): void {

The function takes a Commander program and returns nothing; its job is to extend the program with the init subcommand plus its --batch, --plan, --no-refine, and --concurrency options. The action handler then resolves the user options, calls runInit, and emits either JSON or the human formatter.

The flag parser is intentionally narrow:

• --batch switches the run into the full LLM pipeline (stages 1–4) instead of the deterministic layout.
• --plan requests a heuristic module plan with no LLM calls and no file writes.
• --no-refine is declared as a Commander --no-<flag> option, which means the property on the parsed options is refine (default true). The handler therefore checks opts.refine === false to derive noRefine; the property noRefine is never set by Commander and reading it would silently disable the wrong branch.
• --concurrency <n> is captured as a string and forwarded as batchConcurrency only when explicitly provided; the core validates that it is an integer in 1..16.