pr-monitorlisted

# PR Monitor Follow Steps 1-5 in order. **You may NOT report merge-ready or "ship" until Step 5, and Step 5 has prerequisites that reference every prior step.** Skipping ahead means the prerequisites fail and you must go back. This skill ALWAYS evaluates, replies to, and resolves bot review threads (qodo, CodeRabbit) as part of the workflow. That is core, not optional. ## Step 1: Determine the PR - If a PR number or URL is given, use that. - If on a feature branch: ``` gh pr view --json number,title,url,state,statusCheckRollup,reviewDecision,comments ``` - If no PR exists, say so and stop. Record `owner`, `repo`, and PR `number` for API calls below. ## Step 2: Run a full status pass Run all five checks. You re-run this exact step during follow-up (Step 4), so be consistent. ### 2a. CI checks ``` gh pr checks <number> ``` Report: passed / failed / pending. For failures: `gh run view <run-id> --log-failed`. ### 2b. Review decision ``` gh pr view <number> --json reviewDecision,reviews,latestReviews ``` Report: approved / changes-requested / pending. List reviewers. ### 2c. Unresolved review threads ``` gh api graphql -f query='{ repository(owner: "OWNER", name: "REPO") { pullRequest(number: NUMBER) { reviewThreads(first: 100) { nodes { id isResolved comments(first: 5) { nodes { author { login } body path position createdAt } } } } } } }' ``` List each UNRESOLVED thread: author, file