handle-reviewlisted

# Handle review feedback `/orchd:handle-review <pr>`. Working through the feedback, not GitHub's resolve-conversation button — marking threads resolved stays the reviewer's ([After posting](#after-posting)). **Nothing is posted without a separate go.** Pushing code is fine (your own branch, `--force-with-lease`); posting a comment, filing a story, resolving a thread and re-requesting a review are not. You are in a pane somebody is watching, so ask them things directly with `AskUserQuestion`. `$ORCH_PR` is the PR and `$ORCH_LANGUAGE` is the language to write replies in when a thread does not settle it. `gh` runs inside the PR's own worktree, so it infers the repo; `gh api user --jq .login` is you. ## Fetch ```bash gh api graphql -f query=' query($owner:String!,$repo:String!,$num:Int!){ repository(owner:$owner,name:$repo){ pullRequest(number:$num){ headRefName headRepositoryOwner{login} reviewThreads(first:100){ nodes{ isResolved isOutdated comments(first:20){ nodes{ databaseId author{login} body path line url } } } } } } } ' -F owner=<owner> -F repo=<repo> -F num=$ORCH_PR ``` `gh repo view --json owner,name` gives the two you need. Plus `gh pr view $ORCH_PR --json reviews,comments` for review-level bodies that are not anchored to a line. Skip `isResolved`. **Keep `isOutdated`**: the code moved, the point may still stand. A thread whose last comment is your own is already answered; do not re-answer it. ## Sort Read the code at each thread before judging