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