pr-address-comments_skill

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.