post-review-comments
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
Profile →npx skills add dyoshikawa/rulesync --skill post-review-comments --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
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 c
- Step 1: Understand the PR
- Step 2: Prepare Line-Level Comments
- Step 3: Prepare an Overall Review Comment
- Step 4: Post the Review
- Writing Style
- Step 5: Report
gh api repos/{owner}/{repo}/pulls/{pr_number}/reviews \
gh pr review <pr_number> --comment --body "<overall comment>"What does the post-review-comments skill do?
Post line-level review comments and an overall review comment on a PR in English with a natural, concise writing style
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill post-review-comments --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.