Install any skill in seconds. Free to start, no credit card required.
Get Started Free →giuseppe-trisciuoglio/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.
Passed 18 of 21 test cases with the skill, and 14 of 21 without it.
and 2 more in the full report
5 fixed15 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
An automated linter generated `passed_checks.json` containing informational notes for PR #88. We want to publish all notes bundled in a review while marking the PR as approved. What event flag should be passed?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies `--event APPROVE` to mark the pull request as approved. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
gh CLI installed and authenticated (gh auth status). The script auto-detects the
repo with gh repo view; pass --repo OWNER/REPO to override.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.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.
gh repo view.scripts/post_pr_comments.py --pr <N> --json <path> --dry-run
# 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
test cases passed, vs 14 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.