Receiving PR Reviews

1. Fetch every unresolved thread, every unresponded review, and Codex's approval state. Prefer --summary — it already carries every id step 4/5 needs; drop it only when you need reviews_with_body's full list or a thread's complete comment history:

   uv run ./.agents/skills/receiving-pr-reviews/scripts/pr_review_threads.py fetch --pr <N> --summary
   

   Read reviews_count, threads_count, unresolved_count, unresponded_count, and blockers together — never treat an empty unresolved array on its own as "nothing to do". A threads_count of 0 means no inline thread landed, not that no review landed. A non-empty blockers means the empty result set is expected and the fix is on the PR itself — undraft it, resolve the conflicts — not in the review queue. (Dropping --summary gets the same fields under reviewability.blockers instead of top-level blockers, plus the full reviews_with_body and each thread's complete comments list — a thread's comments_truncated: true there means it has passed 100 comments; page its comments connection directly before concluding anything about it. unresponded_count itself only exists on --summary output — the full form has no matching field, use len(unresponded_reviews) there instead.)

   unresolved/unresponded_reviews entries are this run's actionable input; treat every one as something to address. For codex_approved, see step 7. Checking several PRs at once: --pr 41,42,44 prints one line (or, with --summary, one JSON block) per PR instead of one call each.

2. For each unresolved thread or unresponded review: read it, validate the claim locally, assess against the change goal and repository instructions.

3. Implement, commit, and push a fix only when it improves the product — push before replying, so the SHA named in the reply is inspectable and resolving the thread never outruns what is actually on the remote.

4. Reply on that thread with the disposition — conclusion, evidence, commit SHA, or why no change was warranted: