What is gh-address-comments?

A GitHub pull-request workflow for finding open reviewer comments and conversation threads with the GitHub command-line tool.

It helps inspect a pull request, summarize inline and general comments, address the feedback, and resolve review threads.

It brings scattered review feedback into one triage process so requested changes are less likely to be missed.

gh-address-comments — Skill for Claude Code by ulises-jeremias

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add ulises-jeremias/agent-toolkit --skill gh-address-comments

Clone the repo

git clone --depth 1 https://github.com/ulises-jeremias/agent-toolkit

Made for: Claude Code.

Or install agent-toolkit-complete, the plugin that ships this one along with the rest of its 116 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/gh-address-comments/github.svg)](https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/gh-address-comments)

Your own site

<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/gh-address-comments"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/gh-address-comments/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/gh-address-comments"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/gh-address-comments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 769 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00051	$0.00769
Opus 5	$0.00026	$0.00385
Sonnet 5	$0.00010	$0.00154
Haiku 4.5	$0.00005	$0.00077

Measured 5d ago against content hash 83ac0e2e372d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

gh-address-comments scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/agent-toolkit-complete/.github/skills/gh-address-comments/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Address GitHub PR Comments

Find the open PR for the current branch and walk through its review/conversation comments using gh. Pair with github-cli-workflow when you also need to push changes or update the PR description.

When to use

The current branch has an open PR and reviewers left comments.
The user asks to "address comments", "resolve review threads", or "respond to PR feedback".
You need a summarized view of inline comments + reviews + conversation threads in one call.

Prerequisites

gh (GitHub CLI) installed and on PATH (covered by bootstrap).
gh auth status exits 0. If not, ask the user to run gh auth login once (workflow + repo scopes recommended).
python3 (used by the bundled inspection script).

doctor already reports gh auth status under "Integrations" — confirm it is green before invoking this skill.

Workflow

Verify auth. Run gh auth status. If it fails, stop and ask the user to re-authenticate.
Resolve the PR. Use gh pr view --json number,url,title to confirm a PR is associated with the current branch. If none, surface that and stop.
Fetch all threads in one pass. Run the bundled script:
```
python3 ~/.local/share/agent-toolkit/skills/gh-address-comments/scripts/fetch_comments.py \
  > /tmp/pr-comments.json
```
The script paginates conversation comments, review submissions, and inline review threads (including resolved/outdated state) via gh api graphql.
Summarize for the user. Number every thread/comment and provide a one-line intent for each (e.g. [3] tests/foo.test.ts:12 — reviewer asks for a null check).
Ask which to address. Wait for the user to pick numbers before changing code.
Apply fixes. For each accepted comment, edit the relevant file and stage the change. Do not push or merge from this skill — delegate to github-cli-workflow.
Optional: reply or resolve. Once the user confirms, you can post replies with gh pr comment <pr> --body "..." or resolve threads via the GraphQL resolveReviewThread mutation when explicitly requested.

Read the full file on GitHub · 73 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 73 lines · 51 tokens per session scan A 83ac0e2e372d

Subscribe to this mod's changes

gh-address-comments is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 769 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Claude Code Code review Git and workflow agent-toolkit ai-agents ai-tools cursor github-copilot

active-review

Use when the user wants to prepare for a manual PR code review and asks for help targeting it — a terse PR summary, ranked files to read first, and paste-ready inline comment drafts with GitHub deep-links. Triggers: "active review this PR", "walk me through this PR", "help me review this", "give me inline comments to…

paultyng/skill-issue · 157 tokens

gentle-ai-collab-perfect

Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…

Gentleman-Programming/gentle-ai · 106 tokens

gh-address-comments