fetch-unresolved-comments

Fetch unresolved GitHub pull request review comments via GraphQL API.

1|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/risosach/SupervisorPlusAgents --skill fetch-unresolved-comments-risosach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fetch-unresolved-comments
Source: https://github.com/risosach/SupervisorPlusAgents/tree/main/examples/mlflow_agent_model_example/.claude/skills/fetch-unresolved-comments
Command: npx skills add https://github.com/risosach/SupervisorPlusAgents --skill fetch-unresolved-comments-risosach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually sifting through GitHub Pull Request comments to identify active, unresolved feedback is a time-consuming and inefficient process. This Skill automates the retrieval of only the relevant, pending review comments, allowing you to quickly focus on what needs attention.

Core Features & Use Cases

  • Targeted Feedback: Automatically filters out resolved and outdated comments, presenting only the feedback that requires action.
  • GraphQL Power: Leverages GitHub's GraphQL API for efficient and precise data retrieval, ensuring you get exactly the information you need.
  • Structured Output: Provides a clear JSON output grouped by file path, making it easy to integrate with other tools or for quick analysis.
  • Use Case: A developer needs to quickly review all pending feedback on their pull request. Instead of manually scrolling through potentially hundreds of comments, they use this Skill to get a concise list of only the unresolved issues, enabling them to prioritize and address them efficiently.

Quick Start

Fetch all unresolved comments for PR #1234 in the 'my-org/my-repo' GitHub repository.

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 GitHub pull requests?

This Skill automatically filters unresolved PR review comments from GitHub using the GraphQL API, removing resolved and outdated feedback. It outputs a JSON payload grouped by file path so you see only actionable items requiring attention.

Can I retrieve pending feedback across multiple GitHub repositories?

Yes, this Skill applies to GitHub pull requests across repositories. It uses the GitHub GraphQL API with a token and PR context via environment variables or gh, fetching unresolved comments and producing per-file groupings in JSON format.

What's the best way to organize PR review comments by file for analysis?

This Skill structures GitHub PR comments into a clear JSON output grouped by file path, making it easy to integrate with other tools or quickly analyze which files have pending feedback that needs action.

Do I need to manually parse GitHub GraphQL API responses for PR comments?

No, this Skill handles GitHub GraphQL API queries directly. It requires only a GitHub token and PR context, then automatically retrieves and structures unresolved comments into JSON mappings so you don't parse API responses manually.

How can I automate detection of pending review feedback on pull requests?

This Skill automates retrieval of unresolved PR review comments from GitHub, filtering out resolved and outdated feedback. It eliminates manual scrolling through comments and outputs only active items needing attention in structured JSON format.

What limitations should I know before using GitHub GraphQL for comment retrieval?

This Skill requires a valid GitHub token and PR context provided via environment variables or gh. It filters to unresolved comments only and produces per-file JSON output, making it unsuitable for retrieving all historical comments or operating without authentication.