pr-comments

Fetch, filter, and address GitHub pull request review comments via GraphQL.

49|11|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill pr-comments-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-comments
Source: https://github.com/vstorm-co/agenticos/tree/main/.claude/skills/pr-comments
Command: npx skills add https://github.com/vstorm-co/agenticos --skill pr-comments-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing and acting on PR feedback is tedious: comments are scattered across inline threads, conversation comments, and review summaries, and resolved or outdated threads add noise. This Skill consolidates all review feedback into one structured view and drives a systematic fix-and-commit workflow. ## Core Features & Use Cases - Complete comment retrieval: Uses the GitHub GraphQL API to fetch inline review threads, conversation comments, and review summaries, including isResolved and isOutdated status that REST endpoints do not expose. - Filtering and structured presentation: Skips resolved, outdated, and nit comments by default, then groups inline threads by file path and line number in a unified Markdown report. - Guided fix workflow: Classifies each thread as fix, skip, or ask, applies edits, runs the project's verification command, and commits all fixes in a single commit. - Use Case: A reviewer left 15 comments on your pull request. Ask the agent to address the PR comments, and it checks out the PR branch, lists every actionable thread, fixes the code, runs make check, and pushes one commit. ## Quick Start Ask the agent to fetch and address all review comments on pull request number 42, including any nits.

Frequently Asked Questions about pr-comments

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

FAQPage Schema
How do I list all review comments on a GitHub pull request?▼

Use the GitHub CLI GraphQL API to query reviewThreads, comments, and reviews on the pull request. GraphQL is required because the REST endpoints do not return isResolved or isOutdated flags for inline threads.

How to address PR review comments automatically with an AI agent?▼

The agent fetches all threads, filters out resolved, outdated, and nit comments, then classifies each as fix, skip, or ask. After your confirmation it applies the edits, runs the project verification command, and commits everything in one commit.

Why use GraphQL instead of REST for GitHub PR comments?▼

The REST endpoints pulls/N/comments and pulls/N/reviews do not expose isResolved or isOutdated fields. Only the GraphQL reviewThreads connection returns this data, which is needed to filter stale or already-resolved feedback.

Can I see PR comments without applying any fixes?▼

Yes, request a list-only run and the workflow stops after presenting the structured report. Inline threads are grouped by file path and ordered by line number, with separate sections for conversation comments and review summaries.

What happens if I am on the wrong branch when fixing PR comments?▼

The skill checks out the PR's head branch before reading any file and refuses to continue if the checkout fails or the working tree is dirty. This prevents fixes from landing on an unrelated branch or over uncommitted work.