▶ vg build → ask → impact — multi-stack graph demos (docs)

[vibgrate-team]

▶ Run the interactive CLI simulator →
_{Real recorded runs. Build, ask, and impact on the stacks the docs already replay. No signup.}

Look how clean this is

Code graph → ask → impact. See blast radius before you change code. Watch it run.

vg build

vg ask "how do the apps and shared packages fit together"

vg impact fetchApi

Same three steps, every recorded stack — the Example use cases on vg build, vg ask, and vg impact. The CLI home is vibgrate.com/cli. The graph loop is vibgrate.com/graph.

Build — map the codebase

Ask — navigate in plain language

Impact — blast radius before you edit

Notice: build produces the map; ask returns cited nodes, not a chat essay; impact lists callers of the hub. The Node impact recording targets fetchApi. Watch the player for counts — do not paste a blast-radius table here.

The recorded ask strings match the docs:

• TypeScript: vg ask "how do the apps and shared packages fit together"
• .NET: vg ask "how are the domain, application and infrastructure layers separated"
• Python: vg ask "where are the API routes defined and how is the database accessed"
• Java: vg ask "how are controllers, services and repositories wired together"

New here? Getting started with Vibgrate CLI. More on ask and impact: natural-language questions, impact before a change.

— Vibgrate maintainers