post-review-comments — Claude Code skill: how to install
post-review-comments submits line-level feedback and an overall summary to a GitHub pull request using the gh CLI. Useful for automated reviews in natural English.
MIT ★ 1,636 updated 2026-10-24
npx skills add dyoshikawa/rulesync --skill post-review-comments -a claude-codeWhat post-review-comments does
The skill inspects the pull request diff and description, pinpointing exact lines that need attention regarding bugs, style issues, or questionable logic. Along with specific file paths and line numbers, it drafts a concise overall assessment.
Both line comments and the summary are sent in a single gh api review call. If there are no line-specific remarks, it falls back to standard comment mode with gh pr review --comment. A final report details the PR number and comment tally.
Guidelines enforce an English-only, conversational tone without bot-like headers, dividers, or generic praise. Sending reviews fails immediately if GitHub CLI (gh) is not installed and authenticated.
What it helps with
- submit line-level review comments to a GitHub PR
- publish an overall PR summary alongside inline code remarks
- review changes for the current branch without leaving the terminal
- draft plain English review comments without automated filler
Example prompts for the agent
- Review the pull request for the current branch and post comments
- Post line-level review comments on PR 12
- Inspect the diff of PR #84 and submit an overall review via gh
How to install post-review-comments
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-review-comments -a claude-code2Manually: put the files in place
~/.claude/skills/post-review-comments/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/post-review-comments/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-review-comments -a codex2Manually: put the files in place
.agents/skills/post-review-comments/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-review-comments -a cursor2Manually: put the files in place
.cursor/skills/post-review-comments/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install dyoshikawa/rulesync .rulesync/skills/post-review-comments2Manually: put the files in place
.github/skills/post-review-comments/SKILL.md1Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-review-comments -a gemini-cli2Platform CLI
gemini skills install https://github.com/dyoshikawa/rulesync --path .rulesync/skills/post-review-commentsManually: put the files in place
.devin/skills/post-review-comments/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add dyoshikawa/rulesync --skill post-review-comments -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about post-review-comments
How do I install post-review-comments in Claude Code?
Run npx skills add dyoshikawa/rulesync --skill post-review-comments -a claude-code.
What does post-review-comments do?
It analyzes a PR diff, collects line-specific feedback, writes a concise summary, and submits everything to GitHub in a single review batch.
What external tools are needed for post-review-comments?
It relies on the GitHub CLI (gh) to query API endpoints and post comments, so the tool must be logged in locally.
Source text
SKILL.md · MIT
---
name: post-review-comments
description: >-
Post line-level review comments and an overall review comment on a PR in
English with a natural, concise writing style
targets:
- "*"
---
target_pr = the user's request
If target_pr is not provided, use the PR of the current branch.
## Step 1: Understand the PR
Read the PR diff and description to understand:
- What changed and why
- The scope and impact of the changes
## Step 2: Prepare Line-Level Comments
Identify specific lines in the diff that deserve feedback — bugs, potential issues, style concerns, suggestions for improvement, or questions about intent.
For each comment, note:
- The file path
- The line number (in the new version of the file)
- Your comment text
## Step 3: Prepare an Overall Review Comment
Write a brief overall assessment of the PR. This is a summary-level comment, not a repeat of line-level feedback.
## Step 4: Post the Review
Use a single `gh api` call to submit both line-level comments and the overall comment together as one review:
```bash
gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews \
--method POST \
-f event="COMMENT" \
-f body="<overall comment>" \
-f 'comments[]={...}' ...
```
Each line comment requires: `path`, `line` (line number in the diff's new file), and `body`.
If you have no line-level comments, fall back to:
```bash
gh pr review <pr_number> --comment --body "<overall comment>"
```
## Writing Style
Write in **English only**.
Style guidelines — write like a human teammate, not a bot:
- Use plain paragraphs. Avoid headings (`##`), horizontal rules (`---`), and excessive bullet lists.
- Keep it conversational and direct. Say what matters, skip the filler.
- Do not use phrases like "Great work!" or "LGTM!" unless you genuinely mean it and have nothing else to add.
- Be honest. If something looks off, say so clearly but respectfully.
- Short is fine. A two-sentence comment is better than a five-paragraph essay with no substance.
## Step 5: Report
Output the PR number, a count of line-level comments posted, and a brief summary of the overall comment.
© dyoshikawa · MIT · dyoshikawa/rulesync