Skip to main content
Neroli lets you run a lot of work at once. Review is where that work turns into a decision. You do not have to read every line cold. Ask the agent to review its own work first: explain the change, check the diff, run the right automations, capture browser or simulator evidence when relevant, fix anything obvious, and leave you with a clean summary. Then you decide what lands.
Placeholder image: a review screen showing an agent self-review summary, changed files, verification result, browser evidence, and Merge or Archive.

Review starts with an agent self-review, then ends with your decision: continue, merge, open a pull request, or archive.

​
One session

1

Move it to review

Put substantial work in In Review so it is visible as work awaiting a decision.
2

Steer before implementation

When an agent asks for plan review, command approval, or user input, answer inside the session so the context stays with the work.
3

Ask for self-review

Have the agent review its own branch before you do. It should summarize the change, list risks, inspect the diff, and run the workspace checks.
4

Let it clean up

If the agent finds obvious mistakes, missing tests, formatting issues, or docs gaps, let it fix them in the same session.
5

Read the result

Start from the agent’s review summary, then inspect the files that matter: product code, tests, migrations, scripts, config, docs, and generated artifacts.
6

Verify from the session

Use the same Build, Verify, browser, simulator, or terminal automations attached to that session.
7

Look at evidence

Use browser state, screenshots, simulator output, artifacts, generated docs, logs, and diffs as review evidence.
8

Decide

Move it to Merge, open a pull request, continue the session, manually edit, archive it, or mark it Done after validation.

​
A useful review prompt

​
Many sessions

Parallel sessions are where Neroli opens up. You can let several agents explore, then ask each one to review itself before you compare the results. Common patterns:
  • one session builds a feature while another updates docs
  • several sessions explore different implementations
  • one agent writes tests while another changes the product
  • one cloud session keeps working while you continue locally
Ask each branch for a self-review first. Then compare the summaries, diffs, and verification results. Merge one, merge several in sequence, continue the best session, or combine work manually when that is the right call. The sidebar board makes this easier: keep active work in In Progress, move large changes to In Review, use Merge for candidates that look ready, and keep Done for work you want visible before archiving it.

​
What good evidence looks like

​
Red flags

  • the self-review is vague or skips the risky parts
  • the diff is larger than expected
  • tests were deleted instead of fixed
  • verification ran from another session
  • evidence is missing for a user-visible change
  • cloud returned changes that were not checked locally
  • conflict warnings show another session touched the same file or flow
Agent self-review is a filter, not a rubber stamp. Keep the parts you want.
Next: use Recipes and gotchas for parallel work, cloud handoff, and review checklists.