›_ TvijoRU

TVIJO / KNOWLEDGE

Neovim: a terminal workflow with review

Keep editing, commands and evidence close together, while keeping ownership explicit.

Sources verified · · workflow

Start with one project

Open Neovim in the chosen project directory. Inspect the current diff before asking an assistant to edit. Record the files it may change; existing unsaved or uncommitted work remains protected. A terminal pane is a place to run commands, not permission to run every suggested command.

Move between editor and process

Neovim has an embedded terminal. Use :terminal to start a shell buffer and Ctrl-\ Ctrl-N to return to Normal mode. Keep the editor and a test process in separate splits when that helps review. Check the working directory before commands that write files.

A CLI assistant is a separate process with its own login, permissions and quota. Use an explicitly selected account. Subscription CLI sessions and API-key calls have different accounting; never silently switch between them after a failure.

Finish with a visible handoff

Read the changed diff, run the relevant bounded checks, then capture their exit status and the artifact being reviewed. Describe what was checked and what still needs a native environment. The linked handoff guide defines this evidence boundary; the Harness guide explains how an orchestrator can keep it across jobs.

Read this article on: main · platform

Sources

Runtime verification receipt · 2026-10-24T12:46:04.563248+00:00

Continue in your tool

A button passes the visible text to the selected service. Remove secrets and private data; that service has its own terms and charges.

Desktop links require the installed application. If a link does not work, copy the text.

Article connections

Explicit article links. Select a node to open its article at the top.

Article links · keyboard / text view