Review every pull request
Review tasks run an agent in a separate worktree on the pull request's changes and post the review back — always as a comment, never as an approval.
Review a branch by hand
New task → Review changes, or:
agentctl task create --project prj_123 --title "Review payment refactor" \
--prompt "Focus on error handling and idempotency." --review-head feature/payments --review-base mainThe worker fetches both refs, checks the head out in a separate Git worktree under
.agent-orchestration/worktrees/ — your own checkout is never touched — and gives the agent the diff. The
review is accepted only if the agent changed no files and wrote a valid review (summary, verdict
approve/comment/request_changes, and comments with path, optional line, severity and body). The task
completes with the review in its report: no commit, no branch.
Review pull requests automatically
On a GitHub or GitLab integration, set Review pull/merge requests to When opened or When opened and on every push, and enable the Pull requests (GitHub) or Merge request events (GitLab) webhook event.
- Drafts are skipped. Each head commit is reviewed once.
- The worker's project folder must be a clone whose
originis that repository, so it can fetchpull/<n>/headorrefs/merge-requests/<n>/head. - With a reply token configured, GitHub gets a pull request review with line comments; if GitHub refuses line comments (lines outside the diff), the review is posted again with all comments in its text. GitLab gets one merge request note.
Reviews never block or approve
Reviews are posted as comments, never as approvals or change requests, so they cannot satisfy or block branch protection. The verdict is written in the text.
Make reviews sharper
Install a security review skill at the project scope: every review task then follows its checklist.