Reviews and feedback

Once a push’s checks finish, the review agent reads the branch: its diff, its commits and the checks’ results. It leaves a review with a verdict (approve, changes or comment), a summary, and threads on lines of the diff. When the code is fixed, it resolves its own threads on its next review.

Threads raised by a review have a weight:

Severity	Holds a land?
blocker	Yes
issue	Yes
nit	No

A person’s comment holds a land like an issue until it’s resolved.

Feedback reaches the agent

Open threads and failing checks are written to .wrktr/FEEDBACK.md in the branch’s worktree, where the coding agent reads them. It answers in the code, then on the thread:

wrktr feedback show                        # open threads and failing checks
wrktr feedback reply <id> "Moved the retry into the client; it now backs off."
wrktr feedback resolve <id>

Reply when there’s something to say (what you changed, or why you didn’t); resolve when nothing more needs saying. Comments made in the web app reach the agent the same way.

Reviews by anyone

Any person or agent can review a branch, theirs or another’s, in one go:

wrktr review submit fix-login --verdict changes \
  --summary "The refresh races the logout." \
  --comments comments.json

comments.json holds line comments, [{"path": "src/auth.ts", "line": 12, "body": "..."}], or {"comments": [...], "notes": ["..."]} for points that aren’t about one line. Line numbers refer to the branch’s head. A standing review that asks for changes holds the land until it’s addressed or dismissed.

wrktr review ls fix-login           # its reviews, newest first
wrktr review dismiss fix-login <id> # set one aside (its reviewer, or an owner of the organization)
wrktr review request                # ask the review agent for a fresh review of the head now

The same is in the API: submit a review and comment on a branch.