mcpbeat

Pr Address Comments

google-gemini/pr-address-comments

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.

2k tokens
context cost
the whole folder, loaded on every use
2
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
106350
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/google-gemini/gemini-cli --skill pr-address-comments

What comes with it

5 096 bytes besides the instruction
scripts/fetch-pr-info.js

The instruction itself

1 sections, as written by the author

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.

How to use it

Copy the folder

Take google-gemini/pr-address-comments from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.