playbooks

home / skills / google-gemini / gemini-cli / pr-address-comments

pr-address-comments skill

/.gemini/skills/pr-address-comments

This skill helps you address GitHub PR comments on the current branch by summarizing feedback and guiding focused edits using gh.

npx playbooks add skill google-gemini/gemini-cli --skill pr-address-comments

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.0 KB
---
name: pr-address-comments
description: Use this skill if the user asks you to help them address GitHub PR comments for their current branch of the Gemini CLI. Requires `gh` CLI tool.
---
You are helping the user address comments on their Pull Request. These comments may have come from an automated review agent or a team member.

OBJECTIVE: Help the user review and address comments on their PR.

# Comment Review Procedure

1. Run the `scripts/fetch-pr-info.js` script to get PR info and state. MAKE SURE you read the entire output of the command, even if it gets truncated.
2. Summarize the review status by analyzing the diff, commit log, and comments to see which still need to be addressed. Pay attention to the current user's comments. For resolved threads, summarize as a single line with a ✅. For open threads, provide a reference number e.g. [1] and the comment content.
3. Present your summary of the feedback and current state and allow the user to guide you as to what to fix/address/skip. DO NOT begin fixing issues automatically.

Overview

This skill helps you review and address comments on a GitHub Pull Request for the current branch of the Gemini CLI. It guides you through collecting PR state, summarizing open and resolved review threads, and preparing a plan of action. It requires the gh CLI and the project's fetch script to produce accurate context.

How this skill works

First, run the provided script (scripts/fetch-pr-info.js) to gather PR metadata, diff, commit history, and comments. I read the full output, then classify each review thread as resolved (✅) or open and assign a short reference like [1]. I present a concise summary of outstanding items and let you choose which to fix, skip, or discuss before taking any changes.

When to use it

  • You have active PR comments from reviewers or automated agents on the current branch.
  • You want a clear, actionable summary of which review threads are unresolved.
  • You need to decide which comments to address before pushing new commits.
  • You want to avoid fixing things automatically without review or permission.
  • You need to prepare a response to reviewers listing what was addressed or why not.

Best practices

  • Always run scripts/fetch-pr-info.js locally and read the entire output before deciding.
  • Mark resolved threads in git or GitHub once fixes are committed and verified.
  • Reference comment numbers (e.g., [1]) in your commit messages or PR replies for clarity.
  • Ask for clarification on vague comments instead of guessing changes.
  • Confirm tooling requirements (gh CLI) and authentication before fetching PR info.

Example use cases

  • Summarize a long automated review and identify only the actionable failures to fix.
  • Turn reviewer comments into a prioritized checklist to address in follow-up commits.
  • Prepare a reply to reviewers that explains which comments were resolved and why.
  • Help a contributor decide whether to implement a requested change or discuss alternatives.
  • Collect all open threads so you can batch fixes into a single focused commit.

FAQ

What do I need installed to use this skill?

You need the gh CLI authenticated to the repo and access to run scripts/fetch-pr-info.js locally.

Will the skill change code automatically?

No. It only summarizes and organizes review threads. It waits for your instruction before making any fixes.