Index of every page on this site: llms.txt
All skills
davila7 avatar

/address-github-comments

@053feb2
Run it yourself

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

Use this Skill: https://skilld.dev/gh/davila7/claude-code-templates/address-github-comments

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈32 tokens for metadata: the name and description. ≈268 when used: this file.

Description uses 1.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈128 characters, or 1.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill is functional for managing GitHub PR comments but is susceptible to indirect prompt injection from external contributors' comments.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

  • Runlayer9mo

    1/1 file flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 053feb2. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 10 months ago

README badge

README badge for davila7/claude-code-templates/address-github-comments