add-review-comment
Add a review comment to a GitHub pull request.
Best use case
add-review-comment is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Add a review comment to a GitHub pull request.
Teams using add-review-comment should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/add-review-comment/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How add-review-comment Compares
| Feature / Agent | add-review-comment | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Add a review comment to a GitHub pull request.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Add Review Comment Adds a review comment to a specific line in a GitHub pull request. ## Usage **Single-line comment:** ```bash 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:** ```bash 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
Related Skills
adr-review
Multi-agent debate orchestration for Architecture Decision Records. Automatically triggers on ADR create/edit/delete. Coordinates architect, critic, independent-thinker, security, analyst, and high-level-advisor agents in structured debate rounds until consensus.
address-review
Use when addressing PR review comments from Copilot, Claude, or human reviewers. Critically assesses each comment, recommends action (implement/push-back/discuss), and executes appropriately.
address-pr-comments
Addresses PR review comments by making code changes and posting replies. Takes a PR number or auto-detects from current branch. Use when the user wants to address review feedback, respond to PR comments, fix PR feedback, or says "address comments on PR X".
address-github-comments
Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.
adding-markdown-highlighted-comments
Use when adding responses to markdown documents with user-highlighted comments, encountering markup errors, or unsure about mark tag placement - ensures proper model-highlight formatting with required attributes and correct placement within markdown elements
ad-review
Quality review ads before launch by verifying hook strength, checking proof elements, evaluating CTA effectiveness, and assessing visual quality and authenticity. Use as final check before launching creative or when reviewing team submissions.
actionable-review-format-standards
Standardized output format for code reviews with severity labels, file:line references, and fix code snippets. Use when generating review reports that need consistent, actionable feedback structure.
act-code-reviewer
Review JusticeHub code against ACT ecosystem values. Enforces cultural protocols, ALMA principles, and regenerative design.
accessibility-review
Reviews UI for accessibility issues against WCAG 2.1/2.2 AA. Triggers on "is this accessible?", "check accessibility", or contrast/a11y review requests.
academic-reviewer
Expert guidance for reviewing academic manuscripts submitted to journals, particularly in political science, economics, and quantitative social sciences. Use when asked to review, critique, or provide feedback on academic papers, research designs, or empirical strategies. Emphasizes methodological rigor, causal identification strategies, and constructive feedback on research design.
ac-qa-reviewer
Quality assurance review for implementations. Use when reviewing code quality, checking implementation standards, performing QA cycles, or validating feature quality.
a11y-review
Controleer toegankelijkheid conform WCAG 2.1 AA. Gebruik bij het reviewen van templates, CSS of HTML, of wanneer de gebruiker vraagt om toegankelijkheid te checken.