Spark
Sign In
Skill

Address GitHub PR Comments Systematically

A GitHub CLI workflow skill that addresses pull request review comments and issue feedback, fetching threads, planning fixes, and posting resolution updates.

Get skill
Works with github
Antigravity
Maintainer?
46
Spark score
out of 100
Updated yesterday
Version 13.1.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

01

Fetch and inspect all comments on a GitHub PR.

02

Categorize feedback and plan code modifications.

03

Apply code changes based on user confirmation.

04

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

Capabilities

What this skill does

Review code

Analyzes code for bugs, style issues, and improvements.

Debug

Traces errors to their root cause and suggests fixes.

Generate code

Writes source code or scripts from a description.

Write copy

Drafts marketing, email, or product copy on demand.

Overview

Address GitHub Comments

What it does

This skill provides a workflow for addressing GitHub pull request review comments and issue feedback using the GitHub CLI. It guides you through inspecting comments, categorizing and planning fixes with user confirmation when needed, applying code changes, and responding to comment threads.

How it connects

Use this skill when you need to work through PR review comments or issue feedback systematically. It's applicable when you want to execute the workflow described: fetching comments, planning which to address, making fixes, and posting resolution updates.

Source README

Address GitHub Comments

Overview

Efficiently address PR review comments or issue feedback using the GitHub CLI (gh). This skill ensures all feedback is addressed systematically.

Prerequisites

Ensure gh is authenticated.

gh auth status

If not logged in, run gh auth login.

Workflow

1. Inspect Comments

Fetch the comments for the current branch's PR.

gh pr view --comments

Or use a custom script if available to list threads.

2. Categorize and Plan

  • List the comments and review threads.
  • Propose a fix for each.
  • Wait for user confirmation on which comments to address first if there are many.

3. Apply Fixes

Apply the code changes for the selected comments.

4. Respond to Comments

Once fixed, respond to the threads as resolved.

gh pr comment <PR_NUMBER> --body "Addressed in latest commit."

Common Mistakes

  • Applying fixes without understanding context: Always read the surrounding code of a comment.
  • Not verifying auth: Check gh auth status before starting.

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.