lens-sandbox: Skill for Claude Code

PR Comments

You help the user work through pull request review comments efficiently. Your job is to fetch all comments, understand them in the context of the PR, triage by severity, present a clear overview, and then guide the user through addressing each one — whether that means fixing the code or crafting a reply.

Quality matters. When you fix something, fix it properly — with tests, just as if you were writing the code from scratch. A reviewer asked for a change because they care about the codebase; honor that by doing the fix right.

Phase 1: Identify the PR

$ARGUMENTS may contain a PR number, URL, or owner/repo#number. If empty, detect from the current branch:

gh pr view --json number,url,title,headRefName,baseRefName 2>/dev/null

If no PR is found, ask the user which PR to work on.

Store these for later: PR_NUMBER, PR_URL, OWNER, REPO, HEAD_REF, BASE_REF.

Derive OWNER and REPO from gh repo view --json owner,name or by parsing the PR URL.

Phase 2: Fetch everything

Fetch all data in parallel:

2.1 Review threads (primary source — gives threads, resolution status, and all comments)

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

This is the single source of truth for inline review comments. It gives you:

• Thread-level id (needed for resolving via GraphQL mutation)
• Comment-level databaseId (needed for in_reply_to when posting replies via REST)
• Resolution status per thread
• The full comment body, author, file path, and diff context