agentsclimarketplace

Post review

Skill rperez030/accessible-agent-skills/skills/post-review

Post a collected GitHub PR review with inline comments as a single review submission. Use when the user is ready to post a PR review after all feedback has been gathered.From its SKILL.md

Install
npx -y skills add rperez030/accessible-agent-skills --skill post-review

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 543 tokens by cl100k_base, as published. Nobody here has run it

Post PR Review

This skill posts a GitHub PR review. All feedback must already be collected and agreed upon before invoking this skill.

Rules — follow these exactly, no exceptions

  1. Never post inline comments before the review is ready. This skill is the signal that the review is ready to post. Do not post anything until the user invokes it.

  2. Ask whether to include a summary comment (body). If the user wants one, draft it and present for explicit approval before posting. Do not auto-generate a summary. The summary is posted under the user's name and must reflect their voice and accurately represent the severity of findings. If no summary is needed, use an empty string for the body field.

  3. Always post everything as a single API call using gh api repos/{owner}/{repo}/pulls/{number}/reviews with a JSON body that includes the summary body, the event field, and all inline comments in one array. Never post inline comments separately via /pulls/{number}/comments — that creates multiple disconnected review entries.

  4. Use --input - with a heredoc to pass the full JSON payload, not individual --field arguments. This is the only reliable way to include multiple inline comments in a single call.

  5. Verify the result by checking that only one new review ID appears and that its state matches the intended event (e.g. CHANGES_REQUESTED).

Template

gh api repos/{owner}/{repo}/pulls/{number}/reviews \
  --method POST \
  --input - <<'EOF'
{
  "commit_id": "{full_sha}",
  "event": "REQUEST_CHANGES",
  "body": "{summary comment}",
  "comments": [
    {
      "path": "{file path}",
      "line": {line number},
      "side": "RIGHT",
      "body": "{inline comment text}"
    }
  ]
}
EOF

Valid values for event: REQUEST_CHANGES, APPROVE, COMMENT.

If something goes wrong

If comments landed as separate reviews by mistake:

  1. Delete each inline comment via DELETE /repos/{owner}/{repo}/pulls/comments/{comment_id}
  2. Dismiss the bad review via PUT /repos/{owner}/{repo}/pulls/{number}/reviews/{review_id}/dismissals
  3. Note: GitHub does not allow deleting submitted reviews, only dismissing them — dismissed reviews remain visible in the PR timeline
  4. Repost using the template above

What ships with it: 1 file

2.8 KB alongside SKILL.md

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.