Use

The review loop

1. The agent finishes a non-trivial change, or you ask it to "prepare a review" or "show me what you changed".
2. It writes a review of its own change and checks it against git.
3. It serves the review on localhost and gives you the URL.
4. You read, comment, and approve or submit.
5. On Submit, the agent works through every comment, answers each one, and serves the next round. On Approve, it stops.

The agent does not edit anything while the review is open. The working tree at submission is the baseline for the next round, which shows only what changed since.

You can try the page without installing anything.

Reading a review

The Design tab answers whether the change has the right shape:

• Ideal design: how the agent would build the feature on a clean slate, if that differs from what it built.
• Architecture: the concepts the change touched, the system around them, and how they relate. Above the diagram, the numbered steps of the change link to their sections.
• Decisions: every choice the agent made without you, with the constraint behind it, its cost and the alternatives it rejected.
• Caveats: what will surprise you.

The Implementation tab walks through the diff, one section per touched concept. Each chunk of the diff has a passage above it saying why it exists.

Review Raven resolves every diff from git as you read, so the page shows the working tree, including uncommitted and untracked files. Changed files the review does not describe are listed at the end, so nothing is left out unnoticed.

Commenting

Comment on any line of a diff, on a decision, on a caveat or on the design verdict. The prompt at the bottom takes one overall comment on the change. Comments support Markdown.

From the second round on, the Last round part shows each of your comments with the agent's reply, linked to the section that implements it. Reply again if an answer does not satisfy you.

Approving and submitting

With no comments, the button reads Approve. Once you write anything, it reads Submit. Either one ends the session and closes the server.

Saving a review

:save downloads the review as one self-contained HTML file, including your draft comments. It opens without the server, never changes, and suits sharing or an audit trail of what the agent decided and what you answered.

From a shell:

review-raven review.json --export review.html

Command line

review-raven is on the PATH of the shell the agent spawns.

review-raven --new                # seed a review file for this repository
review-raven review.json --check  # validate and exit
review-raven review.json          # serve it