Skip to main content
Navi ships eight flows whose repository access is read-only. Choose one by the job you need done; use the bare question command before reaching for a heavier search flow.

​
Choose the job

​
Search the repository

Use code-search when you want the repository-search discipline as an explicit flow. It returns a direct answer and citations for lines it read.
For normal questions, prefer the shorter bare command. It adds a grounding check and tells you when to rerun with --deep:

​
Review code changes

​
code-review

With no argument, code-review reviews staged and unstaged changes against HEAD:
Pass a revision or range to review a specific diff:
The result contains structured findings with file, line, severity, category, and summary. An empty diff returns no findings instead of inventing work.

​
pre-pr-review

Use pre-pr-review for the branch-level question: is this ready to open as a pull request?
The flow reviews main...HEAD by default. It returns ready or not_ready, structured findings, and an explicit coverage note. When a large diff is bounded, the result names files that were not reviewed line by line.

​
Shape and judge decisions

​
sharpen

Use sharpen before judgment when the idea is still vague. Each invocation asks one forcing question; continue with the session ID it prints.
It works across five dimensions: the real ask, evidence of the problem, the narrowest useful version, blast radius, and kill condition. It returns ASK until it can produce a concrete brief, then returns READY for handoff to Founder. HUMAN is reserved for a decision outside the agent dialogue.

​
founder-advice

Use founder-advice when you want options, tradeoffs, and one recommendation, not a verdict.
Name a file, diff, or plan when the counsel should be grounded in the repository.

​
founder

Use founder when a concrete decision, design, plan, or artifact needs a hard call:
Founder returns GO, REFINE, or REJECT. A thinly grounded request returns REFINE with the missing evidence named.

​
Check a completion claim

​
edge-walk

edge-walk maps the runtime wiring around a claim, expands the seams it opens, and independently judges the cited evidence. For a person at the terminal, use the check command:
It returns one of CLEAR, DIRECT, REPAIR, BLOCKED, ESCALATE, or COMPLETE, with at most one bounded directive. Return evidence to the same session with the printed -t value. The explicit edge-walk flow accepts JSON through --stdin; use it for integrations. See the Automation contract for that transport.

​
Research the web

Use web-search for current external information:
The result contains an answer and the source URLs it used. Without a valid TAVILY_API_KEY, the flow reports that the web was not searched instead of inventing sources.

​
Inspect any flow

The CLI is the source of truth for installed flows:
catalog includes project, pinned, and built-in sources. A project flow with the same name can override a lower-precedence flow, so check the source label when behavior differs from this page.