Stats
Actions
Tags
From gh-review-comments
List, reply to, resolve, and create GitHub PR review comment threads using gh CLI scripts. Use when managing code review feedback, replying to reviewer remarks, resolving review conversations, creating reviews with line-level comments, or bulk-processing threads by author.
How this skill is triggered — by the user, by Claude, or both
Slash command
/gh-review-comments:gh-review-commentsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
<!-- justify: CF-side-effect All gh API operations target a specific PR the user is actively working on -->
Wraps gh api (REST and GraphQL) via bash scripts to operate on PR review threads. Each action maps to a script in scripts/.
Parse from $ARGUMENTS:
owner/repo (e.g., smykla-skalski/sai) — required--author <login> — Filter threads by reviewer username--thread-id <id> — Target a specific thread by GraphQL node ID (PRRT_...)--reply <message> — Reply to matched threads with this message--resolve — Resolve matched threads (after replying if --reply also set)--unresolve — Unresolve (reopen) matched threads--unresolved-only — Only show/act on unresolved threads (auto-enabled with --reply or --resolve)--create-review — Enter review creation mode (see Phase 3 alternative)| Mode | Flags | Behavior |
|---|---|---|
| List | (no action flags) | Display threads with IDs, author, body, resolution status |
| Reply | --reply <msg> | Reply to matched threads |
| Resolve | --resolve | Resolve matched threads |
| Reply + Resolve | --reply <msg> --resolve | Reply then resolve each thread |
| Unresolve | --unresolve | Reopen resolved threads |
| Create review | --create-review | Interactively create a review with line-level comments |
All scripts live in scripts/ relative to this skill's base directory. Run them directly so users can allow-list by path pattern:
"${CLAUDE_SKILL_DIR}/scripts/<script>.sh" [args...]
scripts/list-threads.shList review threads with metadata via GraphQL.
"${CLAUDE_SKILL_DIR}/scripts/list-threads.sh" <owner> <repo> <pr_number> [--author <login>] [--unresolved-only]
Output: one JSON line per thread with thread_id, comment_id, author, body, path, line, is_resolved, is_outdated, reply_count.
scripts/reply-thread.shReply to a review thread via REST API.
"${CLAUDE_SKILL_DIR}/scripts/reply-thread.sh" <owner> <repo> <pr_number> <comment_id> <body>
comment_id: integer database ID of the top-level comment (from list-threads.sh comment_id field)scripts/resolve-thread.shResolve a review thread via GraphQL.
"${CLAUDE_SKILL_DIR}/scripts/resolve-thread.sh" <thread_id>
thread_id: GraphQL node ID (PRRT_...) from list-threads.sh thread_id fieldscripts/unresolve-thread.shReopen a resolved review thread via GraphQL.
"${CLAUDE_SKILL_DIR}/scripts/unresolve-thread.sh" <thread_id>
scripts/add-review-comment.shManage comments on a pending review via GraphQL. Supports adding (reply/new thread), editing, and deleting comments.
"${CLAUDE_SKILL_DIR}/scripts/add-review-comment.sh" <review_node_id> <body> --reply-to <comment_node_id>
"${CLAUDE_SKILL_DIR}/scripts/add-review-comment.sh" <review_node_id> <body> --new-thread <path> <line> [--start-line <start_line>] [<side>]
"${CLAUDE_SKILL_DIR}/scripts/add-review-comment.sh" --edit <comment_node_id> <body>
"${CLAUDE_SKILL_DIR}/scripts/add-review-comment.sh" --delete <comment_node_id>
review_node_id: GraphQL node ID of the pending review (PRR_...)comment_node_id: GraphQL node ID of the comment (PRRC_...)--reply-to: reply to an existing thread--new-thread: create a new thread on a file/line (single-line or multi-line)--start-line: (optional, with --new-thread) start line for multi-line comments. Required for suggestion blocks that span multiple lines.--edit: edit an existing pending review comment body--delete: delete an existing pending review commentside: RIGHT (default) or LEFTscripts/create-review.shCreate a PR review with line-level comments via REST API.
"${CLAUDE_SKILL_DIR}/scripts/create-review.sh" <owner> <repo> <pr_number> <event> <body> [<comments_json>|-]
event: PENDING, COMMENT, APPROVE, or REQUEST_CHANGES. PENDING omits the event field from the API payload, creating a draft review that is not yet submitted.comments_json: JSON array of comment objects, each with path, line, body (and optional side, defaults to RIGHT)- as last arg to read comments from stdin$ARGUMENTS for owner/repo, PR number, and flagsowner/repo into separate OWNER and REPO variablesowner/repo and PR number are required--reply or --resolve is set, auto-enable --unresolved-only"${CLAUDE_SKILL_DIR}/scripts/list-threads.sh" with owner, repo, PR number, and filters (--author, --unresolved-only)--thread-id is specified, filter output to only that threadIf no action flags are set, stop here.
Read references/gh-api-guide.md for ID type mapping (REST integer IDs vs GraphQL node IDs), reply endpoint constraints, and shell quoting patterns.
For each matched thread, execute the requested action:
Reply (--reply):
comment_id from the thread data"${CLAUDE_SKILL_DIR}/scripts/reply-thread.sh" with owner, repo, PR number, comment_id, and the reply messageResolve (--resolve):
thread_id from the thread data"${CLAUDE_SKILL_DIR}/scripts/resolve-thread.sh" with thread_idReply + Resolve (--reply and --resolve together):
Unresolve (--unresolve):
thread_id from the thread data"${CLAUDE_SKILL_DIR}/scripts/unresolve-thread.sh" with thread_idWhen --create-review is specified, skip Phase 2 actions and instead:
"${CLAUDE_SKILL_DIR}/scripts/create-review.sh" exactly once with the collected datacomment_count from the submitted payload (not from the API response). If the script exits 0, the review and all comments were submitted atomically - treat it as fully successfulNEVER re-run create-review.sh after it exits 0. The GitHub review creation API is atomic: if the call succeeds, the review body and all inline comments were attached.
Running it again creates a duplicate review. There is no partial success - it either all works or the script fails with a non-zero exit.
For reply/resolve/unresolve actions: spawn a general-purpose verification agent via Task. Pass it:
owner/repo#number)reply, resolve, unresolve, or combination)"${CLAUDE_SKILL_DIR}/scripts/list-threads.sh"The agent must:
list-threads.sh with the same owner, repo, PR number, and filters used in Phase 2success, partial, or failed), count of successful operations, count of failed operations, and a list of any failed thread IDs with the reasonDisplay the agent's verification summary to the user along with:
For create-review: do NOT spawn a verification agent. Do NOT re-list threads.
The create-review.sh script output is the sole source of truth.
If it exited 0 and returned a comment_count and html_url, the review was created with all comments attached.
Report the review URL and comment count directly.
--thread-id matches no thread, report "No matching thread found"create-review.sh fails (non-zero exit), report the error to the user. Do not retry automatically - the most common cause is invalid file paths or line numbers not present in the PR diff. Ask the user to verify the comment targets before re-attempting/gh-review-comments smykla-skalski/sai 4
/gh-review-comments smykla-skalski/sai 4 --unresolved-only
/gh-review-comments smykla-skalski/sai 4 --author Automaat
/gh-review-comments smykla-skalski/sai 4 --author Automaat --reply "Fixed in latest push"
/gh-review-comments smykla-skalski/sai 4 --author bartsmykla --reply "Done" --resolve
/gh-review-comments smykla-skalski/sai 4 --thread-id PRRT_kwDOCnTGG85tgSD3 --resolve
/gh-review-comments smykla-skalski/sai 4 --thread-id PRRT_kwDOCnTGG85tgSD3 --reply "Done, thanks!" --resolve
/gh-review-comments smykla-skalski/sai 4 --thread-id PRRT_kwDOCnTGG85tgSD3 --unresolve
/gh-review-comments smykla-skalski/sai 4 --create-review
npx claudepluginhub smykla-skalski/sai --plugin gh-review-commentsFetches 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.
Reads open GitHub PR review comments, triages by severity, applies code fixes, and drafts replies. Use when addressing PR feedback or code review.
Fetches and filters PR review comments, extracts outside-diff-range feedback from review bodies, and resolves threads with proper attribution. Useful when addressing CodeRabbit, Cursor, or human reviewer feedback.