github-pr-comments

Fetches active GitHub PR review comments with diff context and applies each requested change.

Updated Aug 19, 2026
One-click install
npx skills add https://github.com/swcstudiospace/aimeecodes --skill github-pr-comments-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-comments
Source: https://github.com/swcstudiospace/aimeecodes/tree/main/.aimee/skills/github-pr-comments
Command: npx skills add https://github.com/swcstudiospace/aimeecodes --skill github-pr-comments-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Addressing inline code review feedback on a GitHub pull request often means manually clicking through dozens of comments, losing track of which ones are resolved, and missing context around each suggestion. This Skill automates the retrieval of every active review thread and walks through applying each change systematically. ## Core Features & Use Cases - Comment Retrieval: Uses the GitHub GraphQL API via the gh CLI to fetch all unresolved, non-outdated review threads, each paired with its diff hunk for full code context. - Systematic Resolution: Creates one todo item per comment, then applies suggestion blocks verbatim or infers changes from free-form feedback. - Verification: Runs cargo check and cargo nextest run after all comments are addressed to confirm nothing broke. - Use Case: A reviewer leaves 12 inline comments on your Rust PR. Run the Skill to pull every comment with surrounding code, work through them one by one, and verify the build before pushing. ## Quick Start Ask the agent to resolve the review comments on the current pull request, and it will fetch each inline comment with its code context and apply the changes one at a time.

Frequently Asked Questions about github-pr-comments

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

FAQPage Schema
How do I resolve all review comments on a GitHub PR at once?▼

Run the bundled pr-comments.sh script with the PR number to fetch every active review thread with its diff hunk, then create a todo per comment and apply each change. Suggestion blocks are applied verbatim; free-form feedback is interpreted against the surrounding code.

How to fetch GitHub PR review comments from the command line?▼

Use the gh CLI's GraphQL API to query reviewThreads, which exposes isResolved and isOutdated flags that the REST comments endpoint does not provide. The script paginates results and filters to only active threads needing action.

Does this work without specifying a PR number?▼

Yes, the script resolves the PR for the current branch automatically using gh pr view. If the branch has no open PR, it exits with an error asking you to pass a PR number as the first argument.

Why are some review comments missing from the output?▼

The script filters out threads marked as resolved or outdated via the GraphQL isResolved and isOutdated fields. Only active threads that still require action are printed, so already-handled comments are intentionally excluded.

What tools are required to fetch PR review threads?▼

You need the GitHub CLI (gh) authenticated to the repository, plus jq for JSON processing and sed for stripping ANSI color codes. Verification after applying changes uses cargo check and cargo nextest run.