How do I install the Gh Address Comments skill?

Run npx skillmds@latest add jlnbuiles/gh-address-comments in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Gh Address Comments safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gh Address Comments?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gh Address Comments free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gh Address Comments?

jlnbuiles (@jlnbuiles) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gh Address Comments by jlnbuiles — Agent Skill

Name: Gh Address Comments
Rating: 4.2 (5 reviews)
Author: jlnbuiles

Gh Address Comments

Help address review comments on the open GitHub PR for the current branch using gh CLI. Verify gh authentication, fetch unresolved review threads, summarize the actionable items, and implement selected fixes after the user chooses which comments to address.

jlnbuiles Updated Sep 22, 2026

File contents

GitHub Address Comments

Use this skill when the user wants to work through GitHub PR review comments.

Run all gh commands with elevated network access.

Expert Standard

Think like an experienced reviewer and maintainer, not a comment clerk.
Give advice like an expert: separate true defects from preference, explain which comments matter, and do not over-fix.
Execute like an expert: preserve intent, make focused changes, and keep the PR moving.

Communication Style

Summaries should use simple words and short sentences.
Translate each review thread into one plain-English action or response.
Avoid GitHub or architecture jargon when a simpler phrase works.
Make it obvious what needs code, what needs tests, and what only needs a reply.

Inputs

repo: repo path, default .
pr: PR number or URL, optional; default current branch PR

Workflow

Run gh auth status. If auth fails, stop and ask the user to run gh auth login.
Fetch comments with: python "<path-to-skill>/scripts/fetch_comments.py" --repo "." --summary --unresolved-only
Triage each item as:
- code change
- test gap
- docs / explanation
- disagreement / pushback
Present a short numbered list with reviewer, location, summary, and likely response.
Ask which items to address.
Implement only the selected items.
Summarize what changed, what remains unresolved, and what checks were run.

Rules

Prefer unresolved threads first.
Do not force code changes when an explanation is enough.
If a reviewer request is incorrect or conflicts with the codebase direction, explain that before changing code.
Preserve unrelated local changes.
Keep triage expert-level, but phrase the user-facing summary so it is easy to understand quickly.

---name: gh-address-commentsdescription: Help address review comments on the open GitHub PR for the current branch using gh CLI. Verify gh authentication, fetch unresolved review threads, summarize the actionable items, and implement selected fixes after the user chooses which comments to address.---# GitHub Address CommentsUse this skill when the user wants to work through GitHub PR review comments.Run all `gh` commands with elevated network access.## Expert Standard- Think like an experienced reviewer and maintainer, not a comment clerk.- Give advice like an expert: separate true defects from preference, explain which comments matter, and do not over-fix.- Execute like an expert: preserve intent, make focused changes, and keep the PR moving.## Communication Style- Summaries should use simple words and short sentences.- Translate each review thread into one plain-English action or response.- Avoid GitHub or architecture jargon when a simpler phrase works.- Make it obvious what needs code, what needs tests, and what only needs a reply.## Inputs- `repo`: repo path, default `.`- `pr`: PR number or URL, optional; default current branch PR## Workflow1. Run `gh auth status`. If auth fails, stop and ask the user to run `gh auth login`.2. Fetch comments with: `python "<path-to-skill>/scripts/fetch_comments.py" --repo "." --summary --unresolved-only`3. Triage each item as: - code change - test gap - docs / explanation - disagreement / pushback4. Present a short numbered list with reviewer, location, summary, and likely response.5. Ask which items to address.6. Implement only the selected items.7. Summarize what changed, what remains unresolved, and what checks were run.## Rules- Prefer unresolved threads first.- Do not force code changes when an explanation is enough.- If a reviewer request is incorrect or conflicts with the codebase direction, explain that before changing code.- Preserve unrelated local changes.- Keep triage expert-level, but phrase the user-facing summary so it is easy to understand quickly.

Frequently asked questions