@viberaven/cli

@viberaven/cli

Launch readiness for Claude Code, Codex, and other coding agents — same mission map and provider intelligence as VibeRaven Station.

For humans

npx -y @viberaven/cli@beta login
npx -y @viberaven/cli@beta scan --open

Sign in once, then scan with --open to view .viberaven/report.html in the browser (same editorial Mission Map skin as the extension). Or run viberaven with no args for the interactive terminal menu.

Uses the same VibeRaven account and scan quota as the VS Code extension. Does not use your OPENAI_API_KEY — scans go through the managed API after login. See SECURITY.md.

For coding agents

See AGENTS.md. Paste templates/AGENTS.snippet.md into your repo's AGENTS.md. Typical loop:

npx -y @viberaven/cli@beta login   # once
npx -y @viberaven/cli@beta scan    # no --open needed for agents
# read .viberaven/agent-summary.md
npx -y @viberaven/cli@beta prompt
# implement, then scan again

Artifacts

File	Purpose
.viberaven/last-scan.json	Full scan payload
.viberaven/agent-summary.md	Short briefing for agents
.viberaven/report.html	Visual mission map + report/station.css (extension editorial UI)

Switch providers (matches the extension map)

The report shows a provider switch per production area (database, auth, payments, deployment, monitoring, security). Picking one copies a command:

viberaven stack set database neon && viberaven scan --open

You can also set it directly:

viberaven stack set auth clerk   # persists to .viberaven/stack.json
viberaven stack list
viberaven stack clear            # remove all overrides

The next scan re-maps that area using your chosen provider.

Development

From repo root:

npm run cli:build
npm run cli:test
node packages/cli/dist/cli.js scan

Inside packages/cli:

npm run typecheck     # tsc against the shared station engine
npm run demo-report   # render a sample report.html and open it

The report reuses the Station Mission Map visual language (src/report/reportStyles.ts) for parity with the extension.