From claude-coding
Fetches, organizes, and presents GitHub PR comments—issue-level, review bodies, inline—grouped by human/bot with extracted must-fix/optional actionable items.
npx claudepluginhub gupsammy/claudest --plugin claude-codingThis skill is limited to using the following tools:
Fetch, organize, and present all comments on a GitHub pull request — issue-level
Reviews GitHub PR comments by verifying against current code, categorizes issues, replies with reasoning, implements fixes, and resolves threads in one pass.
Reads open GitHub PR review comments, triages by severity and type, applies code fixes, and drafts replies. Use for addressing review feedback.
Fetches GitHub PR review comments via gh CLI and Python script, creates task checklists for threads, links commits to reviews, and blocks completion until all resolved. Use for systematic PR feedback handling.
Share bugs, ideas, or general feedback.
Fetch, organize, and present all comments on a GitHub pull request — issue-level comments, review bodies, and inline review comments — grouped by human vs bot, with actionable items (must-fix, optional) extracted from structured reviews and inline comments.
!git rev-parse --abbrev-ref HEAD!gh repo view --json nameWithOwner --jq .nameWithOwner 2>/dev/null || echo "unknown"!gh pr view --json number,title --jq '"\(.number) — \(.title)"' 2>/dev/null || echo "none"Parse $ARGUMENTS for a PR number or URL. If present, use it directly.
If no arguments provided, check the pre-flight "Current branch PR" value. If it contains a PR number (not "none"), use the detected PR.
If no PR detected, list open PRs:
gh pr list --state open --limit 10 --json number,title,headRefName --jq '.[] | "\(.number)\t\(.title)\t(\(.headRefName))"'
If the list is empty, report "No open PRs found for this repository" and stop. If only one open PR exists, use it directly. Otherwise present options via AskUserQuestion.
Run the fetch script with the resolved PR number (default text output is
pre-formatted and token-efficient; use --output json only for programmatic
consumers):
python3 ${CLAUDE_PLUGIN_ROOT}/skills/get-pr-comments/scripts/fetch_pr_comments.py <PR_NUMBER>
Exit 0 = proceed. Exit 2 = gh auth or network error — report to user.
The script output is already formatted for presentation. If the output starts with "0 human, 0 bot", report "No comments on this PR yet" and skip to Step 4.
Otherwise, relay the script output directly. The output is structured as: actionable items (must-fix, optional) first, then human comments, then bot comments (truncated). Do not reformat or reparse — present as-is.
After presenting comments, offer context-appropriate actions: