wiff-review

Wiff Review

wiff is a terminal-first code-review tool. A review lives in a local session that a human browses in the wiff TUI while an agent reads and writes the same session through the wiff command line. The TUI belongs to the human: never launch or drive it. Do all of your work through the wiff subcommands below.

If there is no session to act on, ask the user to start one with wiff first. The exception is when you are the automation that opens reviews (see below).

Opening or refreshing a review from automation

When your job is to trigger reviews rather than review within a session a human opened, create-or-refresh the session for the current changes in one idempotent step:

wiff new --no-tui --if-needed

It creates a session when none exists for these changes, refreshes one in place when the working copy has moved on, and does nothing when it is already current. With no changes and no session yet, it exits non-zero with "no changes to review". By default it reviews the uncommitted working-tree changes; add --from-base to review the whole branch against its trunk instead. Requires --no-tui.

Selecting the session

Every command acts on the active session for the current project by default, so run wiff from inside the checkout being reviewed and you can usually omit any session flag. When the active session is not the one you want, or the project cannot be derived from the working directory, select it explicitly:

wiff session list
wiff render --session 2br8zf30h
wiff comment add --agent --session 2br8zf30h --review --body "..."

• wiff session list prints the sessions for this project and their ids.
• --session <id> targets a specific session instead of the active one.
• --project <name> forces the project when the working directory cannot name it on its own.

Exploring existing code

Not every review is about a change. To annotate existing code, open an explore review: an empty session over the current working copy, to which you add the files you want to comment on.