addressing-pr-review-comments

Fetches, categorizes, and resolves GitHub PR review comments using the gh CLI.

45.7k|4.4k|Updated Aug 24, 2019
One-click install
npx skills add https://github.com/streamlit/streamlit --skill addressing-pr-review-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addressing-pr-review-comments
Source: https://github.com/streamlit/streamlit/tree/main/.claude/skills/addressing-pr-review-comments
Command: npx skills add https://github.com/streamlit/streamlit --skill addressing-pr-review-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually triaging reviewer feedback on a pull request is tedious: inline review threads, general PR comments, and bot suggestions are scattered across multiple GitHub API surfaces, and it is easy to miss actionable items or waste effort on false positives. This Skill automates the full loop of fetching, analyzing, fixing, and replying to PR review feedback in the streamlit/streamlit repository.

Core Features & Use Cases

  • Comprehensive comment retrieval: Pulls inline review comments, general PR (issue) comments, and unresolved review threads via the gh CLI REST and GraphQL APIs, with pagination support.
  • Intelligent triage: Categorizes feedback using conventional comment types (issue, todo, chore, suggestion, nitpick, question), skips status-only bot messages, and validates bot suggestions before acting on them.
  • Guided fix workflow: Presents a numbered list of actionable items, applies minimal fixes after user selection, flags high-complexity changes, and generates reply text plus thread-resolution commands.
  • Use Case: A reviewer leaves 8 comments on your PR, including two AI bot suggestions. The Skill fetches all feedback, identifies one bot comment as a false positive, applies fixes to the 5 actionable items, and drafts replies and resolve-thread commands for each.

Quick Start

Ask the assistant to address all review comments on the PR for the current branch using the gh CLI.

Frequently Asked Questions about addressing-pr-review-comments

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

FAQPage Schema
How do I address all review comments on a GitHub PR at once?

Use the gh CLI to fetch inline review comments via the pulls comments API and general comments via the issues comments API, then categorize each by conventional comment type. Apply minimal fixes to actionable items and reply or resolve threads afterward.

How to fetch unresolved review threads with the GitHub CLI?

Run gh api graphql with a reviewThreads query filtered by isResolved equals false to list unresolved inline threads with path and line info. For PRs with over 100 threads, use cursor-based pagination with pageInfo.

Should I trust automated bot review comments on pull requests?

Bot suggestions can be false positives, so always validate the flagged issue exists in the code before acting. Status-only bot messages like Snyk check-passed notifications contain no actionable feedback and should be skipped entirely.

Can general PR comments be resolved like inline review threads?

No, only inline review threads have a resolvable state via the resolveReviewThread GraphQL mutation. General PR issue comments have no resolved flag, so they are addressed by applying fixes and posting a reply comment instead.

What should I do when a review comment requires a large refactor?

Flag high-complexity fixes to the user instead of applying them directly. Present the trade-off and let the user decide whether to proceed, push back on the reviewer, or find a simpler approach.