gh-address-comments

Inspect unresolved GitHub pull request review threads and implement selected fixes locally.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill gh-address-comments-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-address-comments
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.ds/codex-home/plugins/cache/openai-curated/github/27651a43bf55185d924f7a1fc49043a0a8be65a0/skills/gh-address-comments
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill gh-address-comments-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Working through pull request review feedback is tedious: inline review threads, resolution state, and outdated comments are hard to track, and flat comment APIs lose thread context. This Skill fetches thread-aware review data via GraphQL, clusters actionable feedback, and guides implementing the selected fixes. ## Core Features & Use Cases - Thread-Aware Review Fetching: Uses a bundled GraphQL script via gh to retrieve reviewThreads, isResolved, isOutdated, and file/line anchors that flat comment surfaces miss. - Feedback Clustering and Scoping: Groups comments by file or behavior area, separates actionable requests from approvals and resolved threads, and confirms scope before editing. - Traceable Fix Implementation: Implements selected fixes locally with each change traceable back to its review thread, then summarizes what was addressed and what was left open. - Use Case: A reviewer left 12 inline comments on your PR. Use this Skill to list the unresolved actionable threads, pick which ones to fix, apply the code changes, and get a summary of what changed. ## Quick Start Use the gh-address-comments skill to review the unresolved feedback on my current branch's pull request and fix the actionable comments.

Frequently Asked Questions about gh-address-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I see unresolved review comments on a GitHub pull request?▼

Use the GitHub GraphQL API through gh api graphql to query reviewThreads with isResolved and isOutdated fields. The bundled fetch_comments.py script paginates through all threads, reviews, and conversation comments for the current branch's PR.

How to fetch inline PR review threads with GitHub CLI?▼

Run the fetch_comments.py script, which resolves the PR from your current branch via gh pr view and calls gh api graphql with a reviewThreads query. Output is JSON containing threads with file paths, line anchors, and resolution state.

Does this work with pull requests from forks?▼

Yes, cross-repository PRs are supported. The script reads headRepositoryOwner and headRepository from gh pr view, so it resolves the correct owner and repo even when the PR originates from a fork.

Why does gh api graphql fail with authentication errors?▼

The GitHub CLI must be authenticated before running GraphQL queries. Run gh auth status to verify, and if it fails, authenticate with gh auth login. Rate limits can also interrupt runs, requiring re-authentication and retry.

Can it reply to or resolve review threads automatically?▼

No, write actions are restricted by design. The Skill does not reply on GitHub, resolve threads, or submit reviews unless the user explicitly requests that write action; it only reads feedback and implements local code fixes.