Code reviews

Branch reviews with iterations linked to nodes.

Flownix keeps code reviews right next to the plan. An agent (or a human) runs a review of a branch, and the result is stored in the project’s “Reviews” tab and linked to the specific nodes that were checked.

How a review is structured

Branch review

Scoped to a project: reviewer, branch name and a starting commit. Created via create_review.

Iterations

Each rerun is a new iteration with a number, a commit hash and a Markdown verdict (add_review_iteration). The full review history is visible.

Node linking

set_review_nodes links a review to tasks/features bidirectionally: the review shows its nodes, and a node shows its reviews (get_node_reviews).

Workflow

An agent with the flownix-review skill runs a review over the branch diff.
The result is saved as a review with a first iteration (commit + verdict).
The review is linked to the reviewed nodes — “review ↔ planning” jumps appear.
After fixes, the next iteration is appended — history accrues instead of being overwritten.