Gemini

Skill 9 of 23

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.

1 minute · 146 words · 1 sections

Install

$ npx skills add google-gemini/gemini-cli --skill pr-address-comments

$ npx skills add google-gemini/gemini-cli

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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.

About this skill

Trigger

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.

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Colophon for this issue

Colophon

How this issue was made

Source

github.com/google-gemini/gemini-cli, branch main, last pushed 8 November 2026.

Licence

Apache-2.0 — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.

Discovery

23 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. 4 distinct layouts observed: .gemini/skills/*/SKILL.md, packages/core/src/skills/builtin/*/SKILL.md, tools/caretaker-agent/cloudrun/triage-worker/.gemini/skills/*/SKILL.md, tools/gemini-cli-bot/.gemini/skills/*/SKILL.md.

Authorship

4 of 23 skills are installed into the repository rather than published from it. They are shelved in the closing “Credited skills” part and remain the work of their own authors. A skill counts as credited when its only copy lives under one agent’s dot directory; visible directories, per-agent mirror sets, and skills installable from this repository on skills.sh all count as published.

Issue colours

Resolved from a curated brand profile — hue 288°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Heading repairs

1 repair applied to this skill so the document has one h1 and no skipped levels:

Shifted “1 heading” from h1 to h2 so the skill title is the only h1.

Spec compliance

2 editorial notes across 2 of 23 skills. They are printed in the margin of each skill rather than as errors here.

Code Explorer — 1 note
Spec Generator — 1 note

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /google-gemini/gemini-cli.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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.

PR Address Comments

Comment Review Procedure

About this skill

Trigger

Colophon

PR Address Comments

Comment Review Procedure

Appendix 9.1

ScriptsJavaScript · 1 file

About this skill

Trigger

Colophon

Appendix 9.1

ScriptsJavaScript · 1 file