Command reference

Overview

The Vibgrate CLI installs as @vibgrate/cli and exposes the vg command (vibgrate is an alias). scan is the default subcommand — bare vg scans the current directory. Never append a trailing . to path-defaulting commands.

This page is the full inventory. Each link opens the detailed command page. Under each set, Typical path is the order most teams run the important commands; the table below it is the full list A–Z.

Drift scoring & supply chain

Typical path: vg init → vg scan → vg baseline → vg report → vg fix

Workspace auth & cloud upload

Sign in, create a DSN for CI, and push scan results. Local drift scoring does not require this — nothing leaves your machine until you push.

Typical path: vg login → vg dsn → vg push → vg logout

Localization

Vibgrate Localize — your application's translation keys and translations, synced between your repo and Vibgrate Cloud. config and format are local-only and free on every plan; the rest need a Team plan or above.

Typical path: vg locale config → vg locale push → vg locale pull

Code graph

Typical path: vg build → vg status → vg ask → vg impact → vg share

AI context & library docs

Typical path: vg serve → vg install → vg lib

Code edits & models

Typical path: vg models → vg code

Holistic Code Specification

Deterministic code facts for Rust, Ruby, PHP, Dart, Swift, Scala, C++, COBOL, and VB6 — extract once, then read, map, or gate the stream.

Typical path: vg hcs extract → vg hcs digest / vg hcs map / vg hcs gate

Diagnostics, IDE & runtime

Typical path: vg doctor → vg lsp → vg daemon

Try without installing

npx @vibgrate/cli scan

After install, prefer vg (not vibgrate) in docs and scripts.