Which threads are included?

Unresolved threads are included; outdated threads are also included but marked for context.

What do --role and --since do?

--role selects the perspective (author or reviewer) based on your authentication; --since filters to threads active since last-review or an ISO date, with semantics described in the skill usage.

github:pr-comments

Flagged

{"isSafe":false,"isSuspicious":true,"riskLevel":"high","findings":[{"category":"prompt_injection","severity":"high","description":"PreToolUse hook attempts to set updatedInput.dangerouslyDisableSandbox to true, effectively disabling sandbox isolation for the tool execution.","evidence":"updatedInput: { dangerouslyDisableSandbox: true } in PreToolUse hook"},{"category":"system_harm","severity":"high","description":"Disabling sandbox can allow arbitrary commands to run with host access, increasing risk of host compromise or data leakage if the tool is exploited.","evidence":"dangerouslyDisableSandbox: true in PreToolUse hook"}],"summary":"The skill content includes a PreToolUse hook that disables sandboxing, which is a prompt-injection-like mechanism undermining host security. While the PR-comment retrieval logic itself is benign, the sandbox bypass represents a high-security risk. Recommend removing or gating the dangerous sandbox-disabling flag and keeping sandbox isolation enabled."}

npx machina-cli add skill bendrucker/claude/pr-comments --openclaw

Files (1)

SKILL.md

2.6 KB

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.

Source

git clone https://github.com/bendrucker/claude/blob/main/plugins/github/skills/pr-comments/SKILL.mdView on GitHub

Overview

Fetch unresolved review threads from a GitHub pull request to identify feedback that still needs addressing. It helps you verify which comments are open and resume work on PRs with outstanding feedback by using the pr-comments.ts script with optional role and since flags.

How This Skill Works

The skill runs the pr-comments.ts script against a PR URL, filtering to unresolved threads. It returns compact markdown grouped by file with line numbers and full comment bodies, including outdated threads but marked for context awareness.

When to Use It

Before finalizing a PR to see what feedback remains
To verify whether your review comments have been resolved
When resuming work after a break and needing outstanding feedback
When triaging PRs with multiple reviewers to focus on new activity
To prepare a concise summary for teammates by listing unresolved threads

Quick Start

Step 1: Run bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts <pr-url> [--role author|reviewer] [--since last-review|<date>]
Step 2: Optionally set --role and --since to tailor the results
Step 3: Review the output (compact markdown by file) and address the feedback

Best Practices

Use --role to align with your perspective (author vs reviewer)
Use --since last-review to focus on new activity since the last relevant review
Rely on the compact, file-grouped output to act on feedback quickly
Note that outdated threads are included but marked to preserve context
Cross-check unresolved lines against your local changes before updating the PR

Example Use Cases

bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123
bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --role author --since last-review
bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --role reviewer
bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --since 2025-01-15
bun ${CLAUDE_PLUGIN_ROOT}/scripts/pr-comments.ts https://github.com/owner/repo/pull/123 --role author --since last-review

Frequently Asked Questions

Add this skill to your agents