playbooks

home / skills / shipshitdev / library / gh-address-comments

gh-address-comments skill

/bundles/github/skills/gh-address-comments

This skill helps you address GitHub PR and issue comments using gh CLI by summarizing threads and proposing fixes with your approval.

npx playbooks add skill shipshitdev/library --skill gh-address-comments

Review the files below or copy the command above to add this skill to your agents.

Files (2)
SKILL.md
1.0 KB
---
name: gh-address-comments
description: Help address review or issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
---

# GH Address Comments

Use this skill when a user wants help resolving PR review or issue comments via the GitHub CLI.

## Workflow

1) Verify auth:
   - `gh auth status -h github.com`
   - If not logged in, ask the user to run `gh auth login`.
2) Identify the PR:
   - `gh pr view --json number,title,url`
   - If no PR is found, ask for the PR URL.
3) Collect comments:
   - Review comments: `gh api repos/{owner}/{repo}/pulls/{number}/comments`
   - Issue comments: `gh api repos/{owner}/{repo}/issues/{number}/comments`
4) Summarize each thread and map to code changes.
5) Propose fixes and get user approval before pushing changes.
6) Draft reply text for each thread and ask before posting to GitHub.

## Notes

- Prefer quoting exact comment text in your summary.
- Keep replies short and specific to the change.

Overview

This skill helps you find and address review or issue comments on the open GitHub pull request for the current branch using the gh CLI. It verifies gh authentication, gathers review and issue comments, summarizes each thread, proposes concrete fixes, and drafts short replies for you to approve before posting. It streamlines comment resolution while keeping you in control of code changes and responses.

How this skill works

First the skill checks gh authentication with gh auth status and prompts you to run gh auth login if you are not logged in. It locates the PR for the current branch using gh pr view and asks for the PR URL if none is found. The skill fetches review and issue comments via gh api, summarizes each thread (quoting the exact comment text when relevant), maps feedback to the impacted code, suggests precise fixes, and drafts reply text. It asks for your approval before making commits, pushing changes, or posting replies to GitHub.

When to use it

  • You want to resolve review comments on the PR for your current branch.
  • You need a concise summary of all review and issue threads before making changes.
  • You prefer proposed code edits and reply drafts generated before committing.
  • You want to confirm gh CLI authentication and guidance to authenticate if needed.
  • You want to ensure replies are short, specific, and tied to code changes.

Best practices

  • Keep replies short and quote the exact reviewer text when summarizing.
  • Review proposed code changes locally before approving automated commits or pushes.
  • Approve each drafted reply before the skill posts to GitHub.
  • If the PR is not detected, provide the PR URL to avoid incorrect lookups.
  • Run gh auth login in the same environment where you plan to push changes.

Example use cases

  • You switched branches and want to address all unresolved review threads on that PR.
  • You need a list of issue comments and suggested code fixes to share with teammates.
  • You want drafted, reviewer-specific replies for a busy maintainer to post quickly.
  • You want the tool to verify gh auth and avoid pushing commits from an unauthenticated session.
  • You need to map review comments to concrete file changes before editing code.

FAQ

What if gh auth status shows I am not logged in?

The skill will prompt you to run gh auth login and will pause until you authenticate; once authenticated it will resume detecting the PR and comments.

Will the skill push code changes automatically?

No. The skill proposes fixes, creates commits locally when you approve, and asks for explicit confirmation before pushing or posting replies.