Reply to and resolve GitHub PR review comments using the GitHub CLI and GraphQL API.
The 'pr-review-reply' skill is designed to assist developers in responding to and resolving GitHub Pull Request (PR) review comments using the GitHub CLI and GraphQL API. It streamlines the process of managing PR feedback in an interactive and collaborative workflow, making it easier for developers to address comments, implement necessary changes, and keep track of progress. By automating the organization of review comments, this skill helps users maintain focus on the important tasks at hand, reducing the time spent on administrative overhead and improving communication with reviewers.
The skill provides a comprehensive workflow that includes fetching review comments, analyzing them, offering recommendations, and then executing the user’s decisions. It categorizes comments based on status, type, and author, and offers clear, actionable guidance on how to respond. The skill also incorporates interactive decision points, allowing users to approve, edit, or skip draft replies, and resolve threads based on reviewer feedback. It helps users follow best practices for PR communication, ensuring that replies are respectful, specific, and well-organized. Additionally, it emphasizes when to resolve comments and when to wait for further input.
This skill is especially valuable for teams working on open-source projects or those with multiple reviewers, where managing review comments efficiently is critical. It's perfect for developers who need to streamline their PR workflows, ensure they address every review comment, and maintain smooth communication with their peers. With its structured, user-friendly approach, 'pr-review-reply' is a must-have tool for anyone looking to improve their code review process on GitHub.
To use this skill, you must have the GitHub CLI ('gh') installed and authenticated. Additionally, you need write access to the repository and an open Pull Request (PR) with review comments.
The skill organizes comments by status (unresolved vs. resolved), type (suggestions, questions, nitpicks, critical issues), and author, helping the user prioritize and address the feedback effectively.
No, the skill does not automatically resolve comments. It presents you with recommendations and allows you to decide when to mark comments as resolved. You must confirm each resolution manually.
No, the skill relies on the GitHub CLI ('gh') for fetching PR data and interacting with GitHub. It cannot function without it.
If you need to make changes to address a review comment after replying, the skill recommends referencing the commit SHA in your reply and resolving the thread once the change has been made.
Quick Setup:
.claude/skills/Repository
stacklok/toolhive