handling-pr-comments

Automates triage, response, and resolution of GitHub pull request review comments.

1|Updated Jun 23, 2026
One-click install
npx skills add https://github.com/seal-harness/seal-harness --skill handling-pr-comments-seal-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handling-pr-comments
Source: https://github.com/seal-harness/seal-harness/tree/main/.agents/skills/handling-pr-comments
Command: npx skills add https://github.com/seal-harness/seal-harness --skill handling-pr-comments-seal-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Addressing PR review feedback is error-prone: developers routinely miss CodeRabbit's "Outside diff range" comments buried in review bodies, forget to reply to individual threads, leave threads unresolved, and stop before checking for new bot comments posted after their latest push. This Skill enforces a complete, repeatable workflow so no reviewer comment is silently ignored. ## Core Features & Use Cases - Systematic Comment Discovery: Filters actionable comments by priority (Critical through Nitpick), extracts out-of-diff-range feedback from review bodies, and detects outdated or out-of-scope threads via the GitHub CLI. - End-to-End Thread Lifecycle: Guides fixing code, replying to each thread with proper attribution, resolving threads via GraphQL, and creating GitHub issues for work exceeding one day. - Post-Push Iteration Loop: Waits for CI checks, detects new bot comments since the last reply, and loops back until zero unaddressed comments remain, verified by a blocking check script. - Use Case: After CodeRabbit and human reviewers leave 20 comments on your PR, run this workflow to triage each one, push fixes, reply with commit references, resolve threads, and confirm nothing new appeared before declaring the PR ready. ## Quick Start Address all review comments on PR number 123, fix the actionable ones, reply to each thread, and resolve everything.

Frequently Asked Questions about handling-pr-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I address all CodeRabbit comments on a GitHub PR?

Fetch inline comments and review bodies with the GitHub CLI, triage each by priority marker, fix the code, reply to every thread with the commit hash, then resolve threads via GraphQL. CodeRabbit's outside-diff-range comments live in review bodies, not threads, so they need separate extraction.

How to resolve GitHub PR review threads programmatically?

Use the GitHub GraphQL API resolveReviewThread mutation with the thread ID obtained from a GraphQL query of the pull request. The REST API cannot resolve threads, so GraphQL is required for this step.

Why do CodeRabbit outside diff range comments not appear as threads?

CodeRabbit posts outside-diff-range feedback inside the review body rather than as inline threads, so they cannot be replied to or resolved individually. You must parse file paths from the review body, fix the code, and acknowledge them with a general PR comment.

Does this workflow work on Windows with Git Bash?

Yes, the scripts run on Windows Git Bash and Mac/Linux. They prefer jq when available and fall back to the gh CLI's built-in jq subset for simpler queries, so the only hard requirement is the GitHub CLI.

What should I do when a review comment is out of scope for my PR?

Treat out-of-scope comments as in scope by default: if the fix takes under a day, implement it in the current PR. For larger or architectural work, create a GitHub issue, link it in your reply, and resolve the thread with that explanation.