PR Review Comments

What it does

When your agent uses it

• You have a list/JSON of review findings (each with a file path
• A message such as summary/failurescenario) and want them published on a PR as inline review comments
• Include post these review comments on the PR
• Associate comments to files in the PR

Example prompts

• “post these review comments on the PR”
• “associate comments to files in the PR”
• “Use the pr-review-comments skill to post review findings from a JSON file as inline comments on a GitHub Pull Request, attaching each comment to its…”
• “/pr-review-comments”

Requirements

• Python 3
• Pre-approved tools (allowed-tools): Read, Write, Bash

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

1. 1Confirm the JSON path and the PR number. If the repo isn't obvious, run gh repo view.
2. 2Dry-run first to see what will be posted and what gets skipped
3. 3Review the "Postable" / "Skipped" counts with the user. If lines were skipped because
4. 4Post for real, choosing the mode (see below)
5. 5Report back the created review/comment URLs and the list of any skipped findings.

What it can do on your machine

Read from SKILL.md and the folder at commit fe73fb3. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Write
  • Bash

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships 1 file in scripts/ (Python), which the agent can run.

  Shell commands in SKILL.md call:

  • gh

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Review Comments loads about 1k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 404 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~117

When it runs · the whole SKILL.md, loaded when a task matches

~1k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Read, Write, Bash

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from giuseppe-trisciuoglio/developer-kit at commit fe73fb3, republished under its MIT licence (© giuseppe-trisciuoglio). 404 words, ~1,040 tokens.

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

allowed-tools

Read, Write, Bash

--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

© giuseppe-trisciuoglio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts, references) in plugins/developer-kit-core/skills/pr-review-comments of giuseppe-trisciuoglio/developer-kit.

• SKILL.md
• references/json-schema.md
• scripts/post_pr_comments.py

Open the folder on GitHubat commit fe73fb3