slidespeak-onbrand: Skill for Claude Code

Review PR Feedback

Go through all review comments on a pull request, research each one, and grill the user on what action to take.

1. Resolve the PR

• If $ARGUMENTS is provided, use it as the PR URL or number.
• Otherwise, detect the PR for the current branch: gh pr view --json number,url,headRefName
• If no PR is found, ask the user for a PR URL or number.

2. Fetch all feedback sources

Fetch both inline review comments and PR-body feedback. Some review agents (for example Greptile) edit the PR description with findings that are not represented as inline review comments, often under headings like Outside diff, Outside the diff, Additional findings, Potential issues, or similar.

# Get PR metadata and body/description. gh pr view supports the `body` JSON field.
gh pr view {number-or-url} --json number,url,title,author,body,comments,reviews

# Get unresolved inline review conversations on changed lines.
# Use reviewThreads instead of /pulls/{number}/comments so resolved conversations can be ignored.
gh api graphql --paginate -f owner='{owner}' -f name='{repo}' -F number={number} -f query='
  query($owner: String!, $name: String!, $number: Int!, $endCursor: String) {
    repository(owner: $owner, name: $name) {
      pullRequest(number: $number) {
        reviewThreads(first: 100, after: $endCursor) {
          pageInfo { hasNextPage endCursor }
          nodes {
            isResolved
            isOutdated
            path
            line
            startLine
            diffSide
            comments(first: 100) {
              nodes {
                id
                url
                body
                author { login }
                createdAt
                outdated
              }
            }
          }
        }
      }
    }
  }'

# Optional: get regular PR conversation comments too, in case agents post feedback there.
gh api repos/{owner}/{repo}/issues/{number}/comments --paginate

Ignore review threads where isResolved is true. For unresolved review threads, use the latest substantive comment in the thread as the primary feedback item and keep earlier thread comments as context. If isOutdated is true, keep the item but mark it as outdated, deprioritize it behind fresh unresolved threads, and re-check the current file before presenting it because the diff context may have shifted. Do not separately include raw /pulls/{number}/comments results unless reviewThreads is unavailable; that REST endpoint includes comments from resolved conversations and can cause already-resolved feedback to be reprocessed.