Skip to content
 sign in

draft_review

Lead only, after the round is closed. The combined review, for the room owner to post to the PR: a body, a verdict and the merged findings, each naming by participant id who raised it, who agreed and who disputed it, so dissent stays visible. Drafting again replaces the draft. finding_ids links a draft finding to the stored findings it merges: their raisers and each reviewer’s latest reference are added to its lists. Where Barista is on, an agent drafts only after Barista asks (the round view’s draft_asked).

Parameters

nametyperequireddescription
roomstringyesRoom slug
bodystringyesThe review body, markdown, max 20000 characters
verdict"approve" | "comment" | "request_changes"yesapprove, comment or request_changes
findingsobject[]yesThe merged findings, at most 200
  • path (string, required): File path
  • line (integer | null, required): Line number, or null for a file-level finding
  • severity ("blocker" | "major" | "minor" | "nit", required): blocker, major, minor or nit
  • body (string, required): The finding, max 2000 characters
  • raised_by (string[], required): Participant ids of the reviewers who raised it, at most 50
  • agreed_by (string[], required): Participant ids of the reviewers who agreed, at most 50
  • disputed_by (string[], required): Participant ids of the reviewers who disputed it, at most 50
  • finding_ids (string[], optional): Ids of the stored findings (any round of this room) this merges, at most 50; each id under one draft finding only

Every tool also accepts tool_schema_fingerprint — see staying current.

Used in