fetch-unresolved-comments

Fetch unresolved GitHub pull request review comments via GraphQL API.

27.4k|6.1k|Updated Jun 5, 2018
One-click install
npx skills add https://github.com/mlflow/mlflow --skill fetch-unresolved-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-unresolved-comments
Source: https://github.com/mlflow/mlflow/tree/main/.claude/skills/fetch-unresolved-comments
Command: npx skills add https://github.com/mlflow/mlflow --skill fetch-unresolved-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tired of sifting through endless GitHub PR comments, including those already resolved or outdated? This Skill cuts through the noise, delivering only the actionable feedback you need to focus on. It ensures you address critical review points efficiently, saving time and reducing cognitive load during code reviews.

Core Features & Use Cases

  • Filter Unresolved Comments: Automatically retrieves only active, unresolved review threads from a GitHub Pull Request.
  • Exclude Outdated Feedback: Ignores comments on lines that have since changed, ensuring the feedback you see is always relevant to the current code.
  • Structured Output: Organizes comments by file path, making it easy to navigate and prioritize feedback.
  • Use Case: Before merging a pull request, quickly get a concise list of all pending feedback to ensure nothing is missed, accelerating your review cycles and improving code quality.

Quick Start

Ensure you have gh CLI installed and authenticated.

Replace <owner>, <repo>, and <pr_number> with your PR details.

GITHUB_TOKEN=$(gh auth token)
uv run python .claude/skills/fetch-unresolved-comments/fetch_unresolved_comments.py <owner> <repo> <pr_number>

Frequently Asked Questions about fetch-unresolved-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I filter unresolved comments from a GitHub pull request?

Unresolved pull request comments are review threads still pending action. This Skill fetches only active, unresolved feedback from GitHub PRs using the GraphQL API, excluding comments on lines that have changed, and outputs them organized by file for quick prioritization.

Can I automatically fetch pending PR feedback across multiple repositories?

Yes. This Skill accepts PR context via environment variables (PR_NUMBER, GITHUB_REPOSITORY) or gh CLI fallback, retrieves unresolved review threads across repositories, and structures output by file path so you can apply it broadly without manual filtering.

What GitHub access do I need to retrieve unresolved pull request comments?

You need the GitHub GraphQL API and a valid GitHub token. The Skill uses gh CLI for authentication; ensure gh is installed and authenticated, then pass your token via GITHUB_TOKEN environment variable to query reviewThreads and their resolution status.

How does this handle outdated feedback on changed lines in a PR?

Outdated feedback—comments on lines that have since been modified—is automatically filtered out. The Skill queries only active review threads, ensuring you see only relevant, actionable feedback tied to the current state of the code.

What's the output format when fetching unresolved PR comments?

The Skill produces JSON output with total unresolved comment count and a by_file object organizing comments by file path, making it easy to navigate feedback and prioritize changes before merging.

Do I need to manually resolve comments before running this Skill?

No. This Skill queries GitHub's resolution status directly via GraphQL, surfacing only threads marked as unresolved. It requires no manual preprocessing and gives you a real-time snapshot of pending feedback.