SkillAgentSearch skills...

pr-review-comments

Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line

Install / Use

npx skills add giuseppe-trisciuoglio/developer-kit --skill pr-review-comments

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

81/100

Supported Platforms

Universal

Our assessment of pr-review-comments

pr-review-comments scores 81/100 on our quality scale, 3491st of 4,705 Development & Engineering skills we index.

Its SKILL.md is 4.1 KB long, split into 7 sections with 1 code example: a solid amount of guidance for an agent.

It has 372 GitHub stars, a meaningful sign that others use it.

Substance
26/30
Structure
15/20
Description
15/15
Adoption
11/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so pr-review-comments is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

pr-review-comments compared with similar skills

All 4 of these similar skills score higher than pr-review-comments; compare them before choosing.

SkillScoreStarsUpdatedFormat
pr-review-comments (this skill)by giuseppe-trisciuoglio813722mo agoSKILL.md
taste-skillby Leonxlnx100120.0ktodayCLAUDE.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
ai-job-searchby ai-job-search-dev10073.0ktodayCLAUDE.md

Frequently asked questions

How do I install pr-review-comments?
Run npx skills add giuseppe-trisciuoglio/developer-kit --skill pr-review-comments. The install tabs above show the steps for each supported agent.
Which AI agents does pr-review-comments work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is pr-review-comments safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is pr-review-comments still maintained?
The repository was last updated about 2 months ago, so pr-review-comments is actively maintained.

name: pr-review-comments description: Posts review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its file and line. Use when you have a list/JSON of review findings (each with a file path, line number, and a message such as summary/failure_scenario) and want them published on a PR as inline review comments. Triggers include "post these review comments on the PR", "associate comments to files in the PR", "publish review findings to PR #N", or having a JSON array of {file, line, summary} to turn into PR comments. allowed-tools: Read, Write, Bash

PR Review Comments

Publish a JSON array of review findings as inline comments on a GitHub Pull Request, each anchored to its file and line. Uses the GitHub API through the authenticated gh CLI, so no token handling is needed.

Prerequisites

  • gh CLI installed and authenticated (gh auth status). The script auto-detects the repo with gh repo view; pass --repo OWNER/REPO to override.
  • The PR number to comment on.
  • A JSON file: an array of objects. Required keys per object: file, line. Message comes from summary and/or failure_scenario (combined into the body), or an explicit body. See references/json-schema.md for the full schema and a sample.

Key constraint: only diff lines are commentable

GitHub only accepts an inline comment if the target line is part of the PR's diff. line is the line number in the new file (use side: "LEFT" for removed lines). The script fetches the PR diff, validates every finding against the actual hunks, and skips any whose line is outside the diff — reporting them at the end so nothing is lost silently. There is no way to attach a line comment to an unchanged, undiffed line.

Workflow

  1. Confirm the JSON path and the PR number. If the repo isn't obvious, run gh repo view.
  2. Dry-run first to see what will be posted and what gets skipped:
    scripts/post_pr_comments.py --pr <N> --json <path> --dry-run
    
  3. Review the "Postable" / "Skipped" counts with the user. If lines were skipped because the diff moved, the line numbers in the JSON may be stale — reconcile before posting.
  4. Post for real, choosing the mode (see below):
    # Grouped (default): one PR review bundling all comments
    scripts/post_pr_comments.py --pr <N> --json <path> --event COMMENT
    
    # Individual: one separate inline comment per finding
    scripts/post_pr_comments.py --pr <N> --json <path> --mode individual
    
  5. Report back the created review/comment URLs and the list of any skipped findings.

Choosing the mode

| Mode | Endpoint | Use when | |------|----------|----------| | grouped (default) | POST /pulls/{n}/reviews | Publishing a set of findings as one review. One notification; can set --event APPROVE \| REQUEST_CHANGES \| COMMENT. | | individual | POST /pulls/{n}/comments | Adding standalone comments incrementally, or when each finding should be its own thread/notification. |

Default to grouped with --event COMMENT unless the user wants a verdict or separate threads.

Options reference

--pr N              PR number (required)
--json PATH         JSON array of findings (required)
--repo OWNER/REPO   Override auto-detected repo
--mode grouped|individual   Default: grouped
--event COMMENT|APPROVE|REQUEST_CHANGES   Grouped-mode verdict (default COMMENT)
--review-body TEXT  Top-level summary body for the grouped review
--commit SHA        Commit to anchor to (default: PR head SHA)
--dry-run           Validate and print payloads without posting

Notes

  • Multi-line range comments: include start_line (and optional start_side) in the JSON object alongside line; the script passes them through.
  • Always --dry-run before a real post on an unfamiliar PR — stale line numbers are the most common failure and the dry-run surfaces them as "skipped" without side effects.
  • The script is the reliable path; don't hand-roll gh api calls for this — it handles diff validation, repo/commit detection, and body assembly consistently.

Related Skills

View on GitHub
GitHub Stars372
CategoryDevelopment
Updated2mo ago
Forks42

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions