From tal
This skill should be used when the user asks to "get PR feedback", "fetch review comments", "show PR comments", "what did reviewers say", "check PR reviews", "address PR feedback", "retrieve PR feedback", or mentions PR review analysis, comment threads, or reviewer feedback. Also invoke when the user provides a GitHub PR comment URL (e.g., https://github.com/org/repo/pull/123#discussion_r456) to fetch that specific comment thread. Provides comprehensive structured access to PR review comments with full conversation context, author information, and thread resolution status.
npx claudepluginhub tal/plugin-marketplace --plugin talThis skill uses the workspace's default tool permissions.
Fetch PR review comments from GitHub as structured threads with conversation context.
Implements structured self-debugging workflow for AI agent failures: capture errors, diagnose patterns like loops or context overflow, apply contained recoveries, and generate introspection reports.
Monitors deployed URLs for regressions in HTTP status, console errors, performance metrics, content, network, and APIs after deploys, merges, or upgrades.
Provides React and Next.js patterns for component composition, compound components, state management, data fetching, performance optimization, forms, routing, and accessible UIs.
Fetch PR review comments from GitHub as structured threads with conversation context.
-a : Show only actionable threads (unresolved + not outdated) - recommended for most use cases-f : Full mode with diff_hunk fields (default: compact without diff_hunks)-o : Sort oldest-first (default: newest-first for most relevant feedback)-v : Verbose diagnostic output to stderrProvides structured access to PR review comment threads with accurate resolution and outdated status that is not easily available through basic gh pr view commands. It:
Prefer this over:
gh pr view --comments (doesn't show threaded conversations or resolution status)gh api calls (requires manual GraphQL query construction)Most common usage (auto-detect PR from current branch, compact by default):
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh
Actionable threads only (recommended - filters to unresolved + not outdated):
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh -a
Full mode with diff_hunks (opt-in to include code context, increases output by 70%):
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh -af
Combined flags example (actionable + full mode + oldest-first):
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh -afo 12345
Specific PR:
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh 12345
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh https://github.com/owner/repo/pull/123
Filter manually with jq (if not using -a flag):
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh | \
jq '[.[] | select(.resolved == false and .outdated == false)]'
Input formats accepted:
12345)https://github.com/owner/repo/pull/123)https://github.com/owner/repo/pull/123#discussion_r123456)Flags:
Returns an array of review threads (sorted newest first by default, use -o for oldest first):
[
{
"thread_id": 123,
"resolved": false,
"outdated": false,
"comments": [
{
"comment_id": 123,
"author": "username",
"body": "comment text",
"path": "file/path.js",
"line": 42,
"original_line": 40,
"html_url": "https://...",
"in_reply_to_id": null,
"created_at": "2025-01-01T00:00:00Z",
"updated_at": "2025-01-01T00:00:00Z",
"commit_id": "abc123"
}
]
}
]
Key fields:
resolved/outdated - Thread-level status (applies to entire thread).comments[0] - Original comment that started the thread.comments[1:] - Replies in the conversationpath, line, original_line - File location context for each commentdiff_hunk - Code context (only included with -f flag, excluded by default)Default behavior:
-o for oldest first)diff_hunk fields, use -f to include them)When the user asks "address the PR feedback":
-a to get only unresolved, non-outdated threadspath and lineRecommended command: ${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh -a
When the user asks "what did reviewers say about X":
When returning to a PR after time away:
-a to see what needs attentionWhen the user provides a comment URL like https://github.com/org/repo/pull/123#discussion_r456:
Use the -a flag for actionable threads, or filter manually with jq:
# Actionable threads (unresolved + not outdated) - built-in with -a flag
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh -a
# Or filter manually with jq
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh | \
jq '[.[] | select(.resolved == false and .outdated == false)]'
# By author
jq '[.[] | select(.comments[].author == "username")]'
# By file
jq '[.[] | select(.comments[0].path | contains("filename"))]'
# Count comments in actionable threads
${CLAUDE_PLUGIN_ROOT}/skills/get-pr-feedback/get-pr-comments.sh -a | \
jq '[.[].comments | length] | add'
For large PRs with many comments:
-a to filter actionable threads (reduces output size)-f only when inline code context is needed (increases output by 70%)[get-pr-comments] Large output detected - wrote to temp file for Claude to read: /tmp/pr-comments-{owner}-{repo}-{pr}.jsonEnable verbose mode (-v flag) for diagnostic output on stderr:
Common issues:
gh auth status and repository permissions.-a flag: All threads are resolved or outdated (expected behavior)-a: Use -v to verify correct PR is queried-a flag to filter first, or ensure PR has <100 threads (GraphQL pagination limit)gh (https://cli.github.com/) and jq, then run gh auth login.gh (GitHub CLI) and jq installed and authenticatedresolved/outdated status[] on error with messages to stderr/tmp/pr-comments-{owner}-{repo}-{pr}.json[get-pr-comments] Large output detected - wrote to temp file for Claude to read: {path}-a flag for actionable threads to minimize output on large PRs