PR Feedback Triage

Retrieve review feedback and status checks for a pull request, classify each item by priority, and propose an ordered action plan. Do not edit files, do not post replies, do not re-run CI.

1. Resolve the PR

• If the argument is a PR number or URL, use it.
• Otherwise, detect from the current branch: gh pr view --json number,url,headRefName,baseRefName,state.
• State the resolved PR (#<n> — <url>) so the user can confirm.

2. Fetch feedback and checks

Run these in parallel (single message, multiple tool calls). Cap any log output aggressively.

• Inline review comments (threaded): gh pr view <n> --json reviewThreads — keep isResolved, isOutdated, path, line, comments[].author/body.
• Review summaries: gh pr view <n> --json reviews — state (APPROVED / CHANGES_REQUESTED / COMMENTED), author, body.
• Conversation comments: gh api repos/{owner}/{repo}/issues/<n>/comments (owner/repo from step 1).
• Status checks: gh pr checks <n>. For each FAIL, fetch a short log tail: gh run view --log-failed --job <job-id> | tail -n 50.