What tools are required?

The gh CLI is required, along with the fetch-pr-info.js script.

Will this fix issues automatically?

No. It only summarizes feedback and guides you on what to address.

How are open threads shown?

Open threads are listed with a reference number like [1] and include the original comment content.

pr-address-comments

npx machina-cli add skill google-gemini/gemini-cli/pr-address-comments --openclaw

Files (1)

SKILL.md

1.0 KB

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

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.
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.
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.

Source

git clone https://github.com/google-gemini/gemini-cli/blob/main/.gemini/skills/pr-address-comments/SKILL.mdView on GitHub

Overview

This skill helps you review and address comments on your PR for the Gemini CLI. It reads PR data via a fetch-pr-info script, then analyzes diffs, commits, and discussions to identify what remains to be addressed. It does not auto-fix; it guides you on next steps.

How This Skill Works

Run scripts/fetch-pr-info.js to retrieve PR data and read the full output. Analyze the diff, commit log, and comments to determine which threads are open vs resolved; resolved threads are summarized with a ✅, while open threads are presented as [N] with the comment content. Present the feedback summary to the user and await guidance; no changes are made automatically.

When to Use It

You need to address specific comments on your Gemini CLI PR using the current branch.
You want a clear view of which review threads are open and which are resolved.
A thread blocks merging and you need a plan before making code changes.
You want to draft targeted responses instead of applying fixes automatically.
You rely on the gh CLI and want human-guided feedback steps.

Quick Start

Step 1: Run scripts/fetch-pr-info.js to fetch PR data.
Step 2: Review the output to identify open vs resolved threads and note any [N] references.
Step 3: Share the summarized feedback with the user and await guidance; no automatic fixes.

Best Practices

Always run the fetch-pr-info.js script and read the entire output.
Prioritize open threads that block merge and require attention.
Use the [N] reference format to track each open comment in your reply.
Keep resolved thread summaries concise and include a ✅.
Pause automatic edits; confirm steps with the user before changing code.

Example Use Cases

Open thread [1] asks for adding unit tests for function parseArgs.
Open thread [2] requests a changelog entry for v2.3.
Open thread [3] suggests switching to a safer default in option parsing.
Open thread [4] asks to elaborate README usage examples.
All threads resolved: the summary ends with a ✅ and no pending items.

Frequently Asked Questions

Add this skill to your agents