How do I install the Unresolved Pr Comments skill?

Run npx skillmds@latest add tomevault-io/unresolved-pr-comments in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Unresolved Pr Comments safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Unresolved Pr Comments?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Unresolved Pr Comments free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Unresolved Pr Comments?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Unresolved Pr Comments by tomevault-io

Name: Unresolved Pr Comments
Author: tomevault-io

Unresolved Pr Comments

Get unresolved review comments from a GitHub pull request. Use this skill when the user asks about PR feedback, review comments, unresolved threads, what reviewers said, CodeRabbit nitpicks, or wants to address PR review feedback. Also use when the user says 'check my PR', 'what's left on my PR', or 'resolve comments'. Use when this capability is needed.

tomevault-io cb8ee8c 2 files · 2.7 KB Updated Sep 17, 2026

File contents

Unresolved PR Comments

Fetch and analyze unresolved review comments from a GitHub pull request.

Usage

Run the script to fetch PR comment data:

bash scripts/unresolvedPrComments.sh [pr-number]

If no PR number is provided, it uses the PR associated with the current branch.

Note: Limited to 100 review threads, 10 comments per thread, and 100 reviews.

Processing Instructions

Using the JSON output from the script:

If error: Display the error message and suggest the fix
If no comments: Report the PR has no pending feedback
If comments exist: Present a brief summary (e.g., "Found 3 unresolved comments and 5 nitpicks")

Then, for EVERY comment (both unresolvedComments AND nitpickComments):

Group comments by file path and read each file once (not per-comment)
If a file no longer exists, note that the comment may be outdated
Assess each comment against the current code. When multiple comments appear at the same file and line, they are part of the same review thread — read them together as a conversation
Group your assessment as follows:

Should address
- Description of the comment with file path(s)
  - Why it's a real issue (bug, a11y, UX, etc.)
Can ignore
- Description of the comment with file path(s)
  - Why: already fixed, not actionable, not worth addressing in this PR, etc.
Net Summary of how many are worth fixing and what kind of issues they are. Offer to fix, but do NOT start until the user confirms.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: unresolved-pr-commentsdescription: Get unresolved review comments from a GitHub pull request. Use this skill when the user asks about PR feedback, review comments, unresolved threads, what reviewers said, CodeRabbit nitpicks, or wants to address PR review feedback. Also use when the user says 'check my PR', 'what's left on my PR', or 'resolve comments'. Use when this capability is needed.---# Unresolved PR CommentsFetch and analyze unresolved review comments from a GitHub pull request.## UsageRun the script to fetch PR comment data:```bashbash scripts/unresolvedPrComments.sh [pr-number]```If no PR number is provided, it uses the PR associated with the current branch.Note: Limited to 100 review threads, 10 comments per thread, and 100 reviews.## Processing InstructionsUsing the JSON output from the script:1. **If error**: Display the error message and suggest the fix2. **If no comments**: Report the PR has no pending feedback3. **If comments exist**: Present a brief summary (e.g., "Found 3 unresolved comments and 5 nitpicks")Then, for EVERY comment (both `unresolvedComments` AND `nitpickComments`):1. Group comments by file path and read each file once (not per-comment)2. If a file no longer exists, note that the comment may be outdated3. Assess each comment against the current code. When multiple comments appear at the same file and line, they are part of the same review thread — read them together as a conversation4. Group your assessment as follows: **Should address** - Description of the comment with file path(s) - Why it's a real issue (bug, a11y, UX, etc.) **Can ignore** - Description of the comment with file path(s) - Why: already fixed, not actionable, not worth addressing in this PR, etc. **Net** Summary of how many are worth fixing and what kind of issues they are. Offer to fix, but **do NOT start until the user confirms**.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/clipboardhealth) — claim your Tome and manage your conversions.

Frequently asked questions