Claude-skill-registry add-review-comment

Add a review comment to a GitHub pull request.

install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/add-review-comment" ~/.claude/skills/majiayu000-claude-skill-registry-add-review-comment && rm -rf "$T"
manifest: skills/data/add-review-comment/SKILL.md
source content

Add Review Comment

Adds a review comment to a specific line in a GitHub pull request.

Usage

Single-line comment:

gh api repos/<owner>/<repo>/pulls/<pr_number>/comments \
  # Body must end with "🤖 Generated with Claude" on a separate line
  -f body=<comment> \
  -f path=<file_path> \
  -F line=<line_number> \
  -f side=<side> \
  -f commit_id="$(gh pr view <pr_number> --repo <owner>/<repo> --json headRefOid -q .headRefOid)" \
  --jq '.html_url'

Multi-line comment:

gh api repos/<owner>/<repo>/pulls/<pr_number>/comments \
  # Body must end with "🤖 Generated with Claude" on a separate line
  -f body=<comment> \
  -f path=<file_path> \
  -F start_line=<first_line> \
  -f start_side=<side> \
  -F line=<last_line> \
  -f side=<side> \
  -f commit_id="$(gh pr view <pr_number> --repo <owner>/<repo> --json headRefOid -q .headRefOid)" \
  --jq '.html_url'

Parameters

  • line
    : Line number in the file (for multi-line, the last line)
  • side
    :
    RIGHT
    for added/modified lines (+),
    LEFT
    for deleted lines (-)
  • start_line
    /
    start_side
    : For multi-line comments, the first line of the range

Best Practices

  • Use suggestion blocks (three backticks + "suggestion") for simple fixes that maintainers can apply with one click

    ```suggestion
    <suggested code here>
    ```
    

    Note: Preserve original indentation exactly in suggestion blocks

  • For repetitive issues, leave one representative comment instead of flagging every instance

  • For bugs, explain the potential problem and suggested fix clearly