mcpbeat

Gh Address Comments

tech-leads-club/gh-address-comments

Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging (use gh-fix-ci), or general Git operations.

This is a copy. The original lives at christophacham/gh-address-comments.

5k tokens
context cost
the whole folder, loaded on every use
3
files
ships runnable scripts
0
copies elsewhere
how many repositories repackaged it
4978
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/tech-leads-club/agent-skills --skill gh-address-comments

The instruction itself

4 sections, as written by the author

PR Comment Handler

Guide to find the open PR for the current branch and address its comments with gh CLI.

Prerequisites: Ensure gh is authenticated before running commands. Check authentication status with gh auth status. If not authenticated, instruct the user to run gh auth login to authenticate with GitHub.

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.

How to use it

Copy the folder

Take tech-leads-club/gh-address-comments from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.