Bidirectional code review. Self-reviews PRs before human review, then responds to human feedback iteratively. Input: PR URLs.
Review PRs for quality or address human review feedback.
You orchestrate this phase. For simple single-PR reviews, you may only need 1-2 workers.
Bidirectional code review: pre-human (self-review to catch issues before a human looks) and post-human (address existing review comments iteratively). Default to bidirectional -- self-review first, then ask if there are human comments to address.
Pre-human: Boromir reviews the full diff, posts structured comments on specific lines, and produces a verdict (approve, request changes, or flag for human attention). For cross-repo PRs or architectural concerns, Gandalf also reviews.
Post-human: Each review comment is dispatched to the appropriate domain worker (Legolas for frontend, Gimli for backend, Frodo for test requests, etc.) who pushes fixes and responds to the comment.
| Worker | subagent_type | When |
|---|---|---|
| Boromir | boromir-the-code-reviewer | Always (primary reviewer) |
| Gandalf | gandalf-the-architect | Cross-repo or architectural PRs |
| Legolas | legolas-the-frontend-dev | Frontend review comments to address |
| Gimli | gimli-the-backend-dev | Backend review comments to address |
| Frodo | frodo-the-test-writer | Test coverage requests |
| Aragorn | aragorn-the-lead-dev | Complex or cross-cutting comments |
Complete when: all review comments are posted (pre-human) or addressed (post-human), CI is green, and a report has been delivered to the user.
## [Code Review] Complete
### Self-Review
- Verdict: {approve | request-changes | needs-human-review}
- Issues found: {N by severity}
### Human Feedback Addressed
- Comments addressed: {N}
- Commits pushed: {N}
### CI Status
- {Green/red after all changes}
### Next Steps
- {Ready for re-review / Ready to merge / Needs more work}