What if gh isn't logged in?

Run gh auth login then gh auth status with the required scopes and retry.

How does it identify the open PR for my branch?

It uses the current Git branch to locate the associated open PR via gh CLI and fetch its comments.

What if I hit rate limits or sandbox blocks?

Prompt gh re-authentication with gh auth login and retry; if sandboxing blocks, re-run with sandbox_permissions=require_escalated.

gh-address-comments

npx machina-cli add skill OutlineDriven/odin-claude-plugin/gh-address-comments --openclaw

Files (1)

SKILL.md

1.3 KB

PR Comment Handler

Guide to find the open PR for the current branch and address its comments with gh CLI. Run all gh commands with elevated network access.

Prereq: ensure gh is authenticated (for example, run gh auth login once), then run gh auth status with escalated permissions (include workflow/repo scopes) so gh commands succeed. If sandboxing blocks gh auth status, rerun it with sandbox_permissions=require_escalated.

1) Inspect comments needing attention

Run scripts/fetch_comments.py which will print out all the comments and review threads on the PR

2) Ask the user for clarification

Number all the review threads and comments and provide a short summary of what would be required to apply a fix for it
Ask the user which numbered comments should be addressed

3) If user chooses comments

Apply fixes for the selected comments

Notes:

If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with gh auth login, then retry.

Source

git clone https://github.com/OutlineDriven/odin-claude-plugin/blob/main/skills/gh-address-comments/SKILL.mdView on GitHub

Overview

This skill locates the open pull request for your current Git branch and helps you address its review comments using the gh CLI. It verifies gh authentication first and guides you through listing threads, selecting which comments to fix, and applying the fixes to the PR.

How This Skill Works

It first ensures gh is authenticated (e.g., gh auth login) and uses gh auth status with escalated permissions. It then runs fetch_comments.py to print all comments and review threads for the current PR, prompts you to number and summarize what’s required, and applies fixes to the selected threads.

When to Use It

You're on a feature branch with an open PR and reviewer comments to address
You want a quick pass to skim all comments before making changes
Your gh session expires or is blocked by sandbox restrictions and you need to re-auth
You need to selectively fix specific comment threads rather than the entire PR
You’re coordinating fixes across multiple threads and want a guided workflow

Quick Start

Step 1: Ensure gh is authenticated (gh auth login) and gh auth status
Step 2: Run fetch_comments.py to list open PR comments for the current branch
Step 3: Number comments, choose which to address, and apply fixes

Best Practices

Always authenticate gh before starting (gh auth login) and verify status with elevated scopes
Run fetch_comments.py to see all comments and threads before acting
Number and summarize what's required for each thread to keep fixes precise
Confirm the selected comments with the user before applying changes
Handle re-auth prompts promptly by re-running gh auth login if needed

Example Use Cases

Frontend feature PR: reviewer left several threading comments; you address 3 threads with minimal changes
Bugfix PR: quickly gather and resolve blocking comments before requesting another review
Contributor on sandbox environment re-auths after a rate-limit prompt and continues
Mobile app PR: address comments across multiple threads to maintain review momentum
CI-related PR: you address build/test comments without leaving the PR blocked

Frequently Asked Questions

Add this skill to your agents