pr-reviewer

Skill: Pull Request Review and Comment Processing

Use this skill when asked to:

• Review a PR — read the diff, assess quality, post a structured review.
• Process review comments — fetch comments left by others, triage them, and act on them.

Required Input

Input	Required	Description
PR number	yes	The GitHub pull request number (e.g. 80)
Product improvement notes	no	Feature/improvement brief that motivated this PR
Implementation plan	no	Ordered task list describing what the PR is supposed to do

If the product improvement or implementation plan are not supplied, infer intent from the PR title, body, and diff — but note the gap when reporting findings.

---

Phase 1 — Gather Context

Run all reads in parallel where possible to minimise latency.

1a. Identify the repository

gh repo view --json nameWithOwner
# → { "nameWithOwner": "dynatrace-oss/dynatrace-snowflake-observability-agent" }

Store OWNER and REPO for all subsequent calls.

1b. Fetch PR metadata and diff

gh pr view <PR#> --json number,title,body,baseRefName,headRefName,state,author,labels,milestone

gh pr diff <PR#>

The diff is the primary artefact for a review. Read it fully before drawing any conclusions.

1c. Fetch all review threads (open and resolved)

Use the GitHub GraphQL API to get rich thread data including file paths, line numbers, diff hunks, and resolution status. Request enough nodes to cover all threads — increase the first: value if the PR is large.

gh api graphql -f query='
{
  repository(owner: "<OWNER>", name: "<REPO>") {
    pullRequest(number: <PR#>) {
      title
      body
      reviewThreads(first: 50) {
        nodes {
          id
          isResolved
          isOutdated
          path
          line
          originalLine
          diffHunk
          comments(first: 10) {
            nodes {
              databaseId
              author { login }
              body
              createdAt
              updatedAt
              minimizedReason
            }
          }
        }
      }
      reviews(first: 20) {
        nodes {
          author { login }
          state
          body
          submittedAt
        }
      }
    }
  }
}'