PR Feedback Triage

Retrieve review feedback and status checks for a pull request, classify each item by priority, and propose an ordered action plan. Triage is read-only — do not edit files, post replies, or re-run CI. Once the user picks which items to act on, hand off to the pr-respond skill, which applies the agreed changes and posts responses (reply + reaction + resolve). Never 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 has no reviewThreads JSON field — it errors with Unknown JSON field. This is where bot findings (Cursor Bugbot, naboo-ai-reviews, etc.) live, so fetch them via GraphQL. The same query also returns the node id (needed by pr-respond to resolve a thread) and each first comment's databaseId (needed for reply/reaction endpoints):