fetch-pr-comments

hvent90's avatarfrom hvent90

Fetch unresolved PR review comments and feedback on the current branch. Use when you need to address outstanding PR review items or see what feedback needs to be resolved. Optionally filter by a specific reviewer.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 21, 2025⬇️1downloads
[Code Review]

When & Why to Use This Skill

This Claude skill streamlines the software development lifecycle by fetching unresolved pull request comments and pending feedback directly into the AI's context. By automating the retrieval of GitHub review threads, it enables developers and AI agents to quickly identify, prioritize, and resolve outstanding items, ensuring a smoother and more thorough code review process.

Use Cases

  • Consolidating Feedback: Quickly aggregate all unresolved comments across a large pull request to create a comprehensive checklist of remaining tasks without leaving the terminal or AI chat.
  • Targeted Resolution: Filter review comments by a specific senior developer or stakeholder to prioritize critical architectural feedback that blocks merging.
  • AI-Assisted Refactoring: Provide the fetched comments as direct context for Claude to automatically generate code fixes that address specific reviewer concerns and 'Changes Requested' states.
  • PR Status Monitoring: Efficiently track the status of pending reviews and unresolved threads to gauge the readiness of a branch for final deployment.
namefetch-pr-comments
descriptionFetch unresolved PR review comments and feedback on the current branch. Use when you need to address outstanding PR review items or see what feedback needs to be resolved. Optionally filter by a specific reviewer.
allowed-toolsBash, Read, Write

Fetch PR Comments

Fetches unresolved review threads and pending reviews from the current branch's pull request.

Usage

Run the script from the repository root:

# Fetch all unresolved comments
./scripts/fetch-pr-comments.sh

# Fetch unresolved comments from a specific user
./scripts/fetch-pr-comments.sh username

Output

Results are saved to /tmp/delete-me/{timestamp}-{repo}-{branch}.json.

Example output structure:

{
  "pr_number": 123,
  "repo": "owner/repo",
  "branch": "feature/example",
  "fetched_at": "2025-12-17T12:00:00Z",
  "filter_user": null,
  "unresolved_threads": [
    {
      "path": "src/example.ts",
      "line": 42,
      "comments": [
        {
          "author": "reviewer",
          "body": "Consider using a more descriptive name",
          "created_at": "2025-12-16T10:30:00Z"
        }
      ]
    }
  ],
  "pending_reviews": [
    {
      "user": "reviewer",
      "state": "CHANGES_REQUESTED",
      "body": "A few items to address",
      "submitted_at": "2025-12-16T10:00:00Z"
    }
  ]
}

What It Captures

  • Unresolved threads: Inline code review comments that haven't been marked as resolved
  • Pending reviews: Overall review submissions (APPROVED, CHANGES_REQUESTED, COMMENTED)

Requirements

  • GitHub CLI (gh) must be installed and authenticated
  • Must be run from within a git repository
  • Current branch must have an open pull request