From fbaabd4fc823e44cb713d8c86bec9a722ba50ebe Mon Sep 17 00:00:00 2001 From: japabu Date: Mon, 12 Oct 2026 16:51:35 +0200 Subject: [PATCH] The orchestrator may ask the owner whether ChatGPT reviews a design pull request, and a reviewer triages what he returns The owner reviews design pull requests himself with ChatGPT's free chat, by hand: automating the chat platform is against its terms, so it is never scripted. He gave the orchestrator leave to ask him: "you can ask me if i can let chatgpt review a design pr". That is leave, not a duty: it names no pull request and no moment to ask. On #863 a single-design review found three design defects that three review rounds had missed, while a one-pass review of all open pull requests found almost nothing new. orchestrator.md's Review and land gains one sentence: the orchestrator may ask the owner whether he will have ChatGPT review a design pull request, and a reviewer triages whatever he returns against the code before anything acts on it. The leave to ask is the owner's ruling; the triage clause is the orchestrator's own design and not part of it. What backs it is #863's triage of his ChatGPT review there: of nine claims, three held, two had already been raised and four did not hold. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_015xhaydXCVRNscoccHYFUWy --- .claude/agents/orchestrator.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/.claude/agents/orchestrator.md b/.claude/agents/orchestrator.md index 84ca7ca3a2..90579a4e59 100644 --- a/.claude/agents/orchestrator.md +++ b/.claude/agents/orchestrator.md @@ -44,10 +44,12 @@ another agent. Every agent's transcript records its usage: a claim about cost is ## Review and land -Start a review whenever one is useful. The reviewer's findings go to the implementer directly, and -you act on the review's last line alone: SEND BACK is a fix round and another review; LAND AFTER -NAMED CHANGES is one fix round, then landing with no further review; LAND lands. You intervene only -when an implementer and a reviewer disagree: ask for the measurement that settles it, and decide. +Start a review whenever one is useful. You may ask the owner whether he will have ChatGPT review a +design pull request, and a reviewer triages whatever he returns against the code before anything +acts on it. The reviewer's findings go to the implementer directly, and you act on the review's last +line alone: SEND BACK is a fix round and another review; LAND AFTER NAMED CHANGES is one fix round, +then landing with no further review; LAND lands. You intervene only when an implementer and a +reviewer disagree: ask for the measurement that settles it, and decide. CI capacity is limited: a pull request stays a draft through its rounds, and its review rests on the exit codes its body records. To land one, `gh pr ready` and `gh pr merge --auto --merge` put it in