Expand description
Read-only code review.
A review is a detached, read-only sub-turn that inspects a diff and
emits structured ReviewFindings instead of editing the workspace. The
findings are surfaced in the TUI and can optionally be handed to a
ReviewPublisher — a pluggable extension service that submits them to an
external platform (GitHub pull-request reviews, an issue tracker, chat).
Core code only sees these types: publishers are registered on the extension registry like any other service and resolved by id.
Structs§
- Review
Code Location - Review
Destination - Free-form publish destination; each publisher interprets
targetandoptionsin its own terms. - Review
Finding - Review
Line Range - Inclusive 1-based line range inside a file.
- Review
Output - Structured result of a review turn. Every field is optional so a partially parsed model response still round-trips.
- Review
Publish Request - Review
Publish Result - Review
Publish Skip - A finding the publisher could not place (e.g. outside the reviewed diff).
- Review
Publisher Capabilities - Review
Publisher Descriptor - Review
Request - Resolved, model-facing review request: the product of a
ReviewTargetand the current version-control state.
Enums§
- Review
Delivery - Whether the caller waits for the review turn or is notified later.
- Review
Priority - Severity of a finding.
P0is the most severe;P2is the default when the model omits one. - Review
Publish Error - Review
Target - What the reviewer should look at. Resolved against the workspace’s version
control provider to produce a
ReviewRequest.
Traits§
- Review
Publisher - Submits review findings to an external platform. Implemented by
roder-ext-*crates and registered on the extension registry; nothing in core knows about any concrete platform.