Address github comments

Skill sickn33/agentic-awesome-skills/plugins/agentic-awesome-skills-claude/skills/address-github-comments

AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 1,987+ agentic skills. Includes CLI, local MCP, catalog, plugins, and Workbench.

Install

npx -y skills add sickn33/agentic-awesome-skills --skill address-github-comments

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.

SKILL.md

1.7 KB, 326 tokens by cl100k_base, as published. Nobody here has run it

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.