comments

Fetch active GitHub Pull Request comments and format them into Markdown.

3|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/pedropaulovc/agent-plugins --skill comments-pedropaulovc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comments
Source: https://github.com/pedropaulovc/agent-plugins/tree/main/plugins/pr-comments/skills/comments
Command: npx skills add https://github.com/pedropaulovc/agent-plugins --skill comments-pedropaulovc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, curl, cygpath, bash, find, jq.

What problem does it solve?

This Skill eliminates the time-consuming process of manually collecting unresolved GitHub Pull Request comments and reorganizing them so an AI can help you triage, draft replies, and close the loop.

Core Features & Use Cases

  • PR comment export: Fetches active (unresolved) PR review threads plus top-level issue comments tied to the PR.
  • Thread-aware formatting: Produces a single Markdown file formatted for LLM consumption, including code context and reply commands.
  • Optional inclusion of resolved threads: Supports --include-resolved to include resolved review threads when you want fuller history.

Quick Start

Ask the AI to run the comments Skill for your current PR so you get a formatted Markdown report of unresolved PR comments ready for drafting replies.

Frequently Asked Questions about comments

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

FAQPage Schema
How do I export GitHub pull request comments for LLM review?

You can export GitHub pull request comments for LLM review by running a local collector script that fetches unresolved PR threads via the GitHub API. It formats the comments into a single Markdown file, adding code context and reply commands for AI-assisted triage.

What is the best way to automate drafting replies for unresolved PR comments?

Automating reply drafting for PR comments is best handled by exporting unresolved threads into an LLM-ready Markdown package. This feeds the AI full code context and comment history, enabling it to triage feedback and propose responses directly.

Do I need gh and jq installed to export PR comments?

Yes, you need gh, jq, curl, and bash installed locally to export PR comments. The collector script relies on these command-line dependencies to execute GitHub API calls, parse JSON responses, and generate the final LLM-ready Markdown output file.

Can I include resolved GitHub PR threads when exporting comments for context?

Yes, you can include resolved GitHub PR threads when exporting comments by using the --include-resolved argument. This fetches resolved review threads alongside active ones, providing the LLM with a fuller conversation history for drafting responses.

How does thread-aware formatting help with pull request comment triage?

Thread-aware formatting helps with pull request comment triage by organizing active review threads and top-level issue comments into a single Markdown file. This structure includes code context and reply commands, making it easier for an LLM to parse and respond to feedback.

What are the limitations of using a local bash script for PR comment collection?

A limitation of using a local bash script for PR comment collection is its dependency on a specific local environment requiring bash, cygpath, and gh. It operates as a command-line collector rather than a continuous integration service, focusing on on-demand export.