What does the Address GitHub Comments skill do?

This skill fetches PR review comments using GitHub CLI, categorizes them, proposes fixes for each comment, applies the code changes, and posts responses to each thread marking them as addressed.

What are the main GitHub CLI commands this skill uses?

The skill uses `gh auth status` to verify authentication, `gh pr view --comments` to fetch PR comments, and `gh pr comment` to post responses to threads.

When should I use this skill?

Use this skill when a PR has accumulated review comments or issue feedback that need to be worked through systematically, with each comment read in context, fixed in code, and responded to in the thread.

What are the key failure modes to avoid?

The skill flags two main mistakes: applying fixes without reading the surrounding code context, and skipping the `gh auth status` check before starting.

Skill

Address GitHub PR Comments Systematically

Name: Address GitHub Comments
Availability: OnlineOnly
Author: Antigravity

Skill that systematically works through GitHub PR review comments via the gh CLI: inspect, plan, fix, and respond.

Get skill

Works with github

Antigravity

Own this? Claim it

Spark score

out of 100

Updated 5 days ago

Version 15.8.0

Add to Favorites

Why it matters

Streamline your code review process by systematically addressing feedback on GitHub Pull Requests. This skill helps you manage comments, propose fixes, and respond efficiently.

Outcomes

What it gets done

Fetch and inspect all comments on a GitHub PR.

Categorize feedback and plan code modifications.

Apply code changes based on user confirmation.

Respond to resolved comment threads.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/ag-address-github-comments | bash

Overview

Address GitHub Comments

A skill for systematically addressing GitHub PR review comments using the gh CLI: inspecting, planning fixes, applying them, and responding to threads. Use when a PR has accumulated review comments needing systematic follow-through; always read surrounding code context before applying a fix.

What it does

This skill efficiently addresses PR review comments or issue feedback using the GitHub CLI (gh), ensuring all feedback is addressed systematically rather than piecemeal. It fetches the current branch's PR comments (gh pr view --comments), categorizes them and proposes a fix for each - waiting for user confirmation on priority order if there are many - applies the code changes for the selected comments, and responds to each thread once fixed (gh pr comment <PR_NUMBER> --body "Addressed in latest commit.").

gh pr view --comments

When to use - and when NOT to

Use this when a PR has accumulated review comments or issue feedback that need to be worked through systematically - reading each comment in context, fixing the underlying code, and closing the loop by responding to the thread.

Not a substitute for actually understanding the surrounding code before applying a fix - the skill's own common-mistakes list flags applying fixes without reading context as a key failure mode, along with skipping the gh auth status check before starting.

Inputs and outputs

Inputs: an authenticated gh CLI session and a PR/branch with existing review comments or issue feedback.

Outputs: applied code fixes for the addressed comments, and posted PR comments marking each addressed thread as resolved.

Integrations

GitHub CLI (gh), specifically gh auth status, gh pr view --comments, and gh pr comment.

Who it's for

Developers working through a backlog of PR review comments who want a systematic inspect-plan-fix-respond loop rather than addressing feedback ad hoc.

FAQ

Common questions

Discussion