paparats-mcp: Skill for Claude Code

/review-pr-comments — evaluate PR feedback and fix valid issues

User-invoked only. $ARGUMENTS is an optional PR number; if empty, auto-detect from the current branch.

All GitHub interaction goes through gh CLI — never the GitHub MCP server. The MCP server is incomplete (missing endpoints for review-thread resolution, partial coverage of comment surfaces).

1. Identify the PR

If $ARGUMENTS has a number, use it.

Otherwise:

BRANCH=$(git branch --show-current)
gh pr list --head "$BRANCH" --json number,title,url --jq '.[0]'

If no open PR for the branch, stop and tell the user.

Capture OWNER, REPO, PR for the rest of the run:

gh repo view --json owner,name --jq '"\(.owner.login) \(.name)"'

2. Fetch comments — THREE separate surfaces

GitHub exposes PR feedback in three places. Missing any one means you'll miss real comments. Always check all three.

2a. Inline review comments (line-anchored)

These are the most common — Gemini/Claude/Copilot bots, human reviewers' line-level comments.

gh api "repos/$OWNER/$REPO/pulls/$PR/comments" --paginate \
  --jq '.[] | {id, path, line, body, user: .user.login, in_reply_to_id, html_url}'

Fields you need: id (REST numeric, used for reply), path, line, body, user.login, in_reply_to_id (non-null = follow-up reply, ignore the duplicates).

2b. Inline review threads (for resolution)

To resolve a thread you need its GraphQL node ID. Fetch in one query and correlate by databaseId ↔ REST id:

gh api graphql -f query='
  query($owner: String!, $repo: String!, $pr: Int!) {
    repository(owner: $owner, name: $repo) {
      pullRequest(number: $pr) {
        reviewThreads(first: 100) {
          nodes {
            id
            isResolved
            isOutdated
            path
            line
            comments(first: 1) { nodes { databaseId author { login } body } }
          }
        }
      }
    }
  }' -F owner="$OWNER" -F repo="$REPO" -F pr="$PR"