pr-review-subscribe

pr-review-subscribe

PR review cycle with provider abstraction: review acquisition and thread processing are separate concerns.

provider = auto | copilot-review | codex | external | existing

Review acquisition (provider-specific):
  copilot-review → Phase 1S (watch/subscribe/complete)
  codex          → Phase W  (post @codex review comment, wait)
  external/human → Phase W  (wait for user signal)
  existing       → skip directly to Phase U1

Unified Review Thread Handling (all providers):
  Phase U1 → Phase U2 → Phase 3 → Phase 4 → Phase U5 → Phase U6

If server/tool names differ, load references/tool-template.md and map placeholders before starting.

Required Surfaces

Placeholder	Purpose	When used
{CRM}	Copilot review MCP tools: review status, request, watch start/cancel	copilot-review acquisition only
{GH}	GitHub issue/PR comment tools	All providers
{RSRC}	MCP resource operations: subscribe/read/unsubscribe or SDK wrapper	copilot-review acquisition only

copilot-review acquisition minimum operations:

• {CRM}:get_copilot_review_status
• {CRM}:request_copilot_review
• {CRM}:start_copilot_review_watch
• {CRM}:cancel_copilot_review_watch
• {CRM}:get_copilot_review_watch_status (fallback polling only)
• {RSRC}:resources/subscribe equivalent for the watch resource
• {RSRC}:resources/read equivalent for the watch resource
• {RSRC}:resources/unsubscribe equivalent for the watch resource

Unified thread handling minimum operations (all providers):

• gh CLI (for gh api GraphQL and REST calls)
• {GH}:add_reply_to_pull_request_comment (map actual name via references/tool-template.md)
• {GH}:add_issue_comment (for PR summary comment and re-review requests)
• {GH}:create_issue (for follow-up issue tracking)

Flow

Phase 0: provider selection
  |
  +--> existing threads detected --------> Phase U1
  |
  +--> copilot-review --> Phase 1S -------> Phase U1
  |
  +--> codex/external --> Phase W ---------> Phase U1 (on user signal)

Phase U1 -> Phase U2 -> Phase 3 -> Phase 4 -> Phase U5 -> Phase U6
                                                             |
                        READY_TO_MERGE <-------- unresolved=0
                             |
                   Phase 6.5 -> Phase 6.6 -> Phase 7 -> Phase 8

Phase U6 re-review policy:
  copilot-review  → structured: Phase 1S loop (max cycles)
  codex/external  → message-based: post comment → WAITING_FOR_REVIEW → stop
  (on ESCALATE or max cycles exceeded → Phase 6.5)

Phase 1S detail (copilot-review acquisition):
  1S-A: Start Watch
  1S-B: Native resources/subscribe  --> success: wait for notification
         |
         | unavailable or failed
         v
  1S-B2: SDK Wrapper subscription   --> success: run wrapper, wait for output
         |
         | not found or failed
         v
  1S-C: Fallback Polling            (last resort only)