How do I install the Githubpr Comments skill?

Run npx skillmds@latest add tomevault-io/githubpr-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 Githubpr Comments safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Githubpr 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 Githubpr Comments free to use?

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

Who published Githubpr Comments?

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

Githubpr Comments by tomevault-io — Agent Skill

Name: Githubpr Comments
Author: tomevault-io

Githubpr Comments

Fetch unresolved review comments from a GitHub pull request. Use when checking what review feedback needs to be addressed, whether review comments have been resolved, or resuming work on a PR with outstanding feedback. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

PR Review Comments

Fetch unresolved review threads from a GitHub pull request, filtered for context efficiency. Avoids flooding the context with resolved threads. Outdated threads are included but marked.

Usage

bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts <pr-url> [--role author|reviewer] [--since last-review|<date>]

Arguments

<pr-url> — GitHub PR URL (e.g., https://github.com/owner/repo/pull/123)
--role — author or reviewer (default: auto-detect based on authenticated user)
--since — Filter to threads with activity since: last-review or ISO date

Role

author (default when authenticated user is the PR author): Shows all unresolved threads — feedback that needs to be addressed.
reviewer (default when authenticated user is not the PR author): Shows only unresolved threads started by the authenticated user — checks whether comments have been resolved.

Since

last-review: Scopes to threads with activity since the last relevant review.
- As author: since the most recent review by a human other than you (bot reviews are excluded)
- As reviewer: since your most recent submitted review
ISO date: Explicit cutoff (e.g., 2025-01-15)

Examples

# What's unresolved? (auto-detect perspective)
bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123

# As author: what new feedback since the last review?
bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --role author --since last-review

# As reviewer: are my comments resolved?
bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --role reviewer

Output

Compact markdown grouped by file with line numbers and full comment bodies — enough to act on the feedback directly without additional API calls.

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

---name: githubpr-commentsdescription: Fetch unresolved review comments from a GitHub pull request. Use when checking what review feedback needs to be addressed, whether review comments have been resolved, or resuming work on a PR with outstanding feedback. Use when this capability is needed.---# PR Review CommentsFetch unresolved review threads from a GitHub pull request, filtered for context efficiency. Avoids flooding the context with resolved threads. Outdated threads are included but marked.## Usage```bashbun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts <pr-url> [--role author|reviewer] [--since last-review|<date>]```## Arguments- `<pr-url>` — GitHub PR URL (e.g., `https://github.com/owner/repo/pull/123`)- `--role` — `author` or `reviewer` (default: auto-detect based on authenticated user)- `--since` — Filter to threads with activity since: `last-review` or ISO date## Role- **author** (default when authenticated user is the PR author): Shows all unresolved threads — feedback that needs to be addressed.- **reviewer** (default when authenticated user is not the PR author): Shows only unresolved threads started by the authenticated user — checks whether comments have been resolved.## Since- `last-review`: Scopes to threads with activity since the last relevant review. - As author: since the most recent review by a human other than you (bot reviews are excluded) - As reviewer: since your most recent submitted review- ISO date: Explicit cutoff (e.g., `2025-01-15`)## Examples```bash# What's unresolved? (auto-detect perspective)bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123# As author: what new feedback since the last review?bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --role author --since last-review# As reviewer: are my comments resolved?bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --role reviewer```## OutputCompact markdown grouped by file with line numbers and full comment bodies — enough to act on the feedback directly without additional API calls.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/bendrucker) — claim your Tome and manage your conversions.

Frequently asked questions