Install any skill in seconds. Free to start, no credit card required.
Get Started Free →saffron-health/get-pr-reviews
Get nicely formatted output of the last review comments on a PR. Used internally by other skills.
Passed 18 of 21 test cases with the skill, and 11 of 21 without it.
and 5 more in the full report
8 fixed11 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
What string prefix should precede the line number under each file header when formatting PR comments?
| Checked | Without skill | With skill |
|---|---|---|
| Formats line designation as Line followed by the line number | Missed | Passed |
The instructions your model reads when the skill loads.
Get nicely formatted review comments for a pull request, grouped by file and line with proper comment threading.
Determine PR number: If not provided, look up the associated PR for the current branch using:
gh pr view --json number --jq '.number'
Get formatted review comments: Use the GitHub API to fetch and format all line-specific review comments:
gh api repos/:owner/:repo/pulls/{PR_NUMBER}/comments --jq '
group_by(.path, .line) |
map({
path: .[0].path,
line: .[0].line,
comments: sort_by(.created_at)
}) |
sort_by(.path, .line) |
map(
"**\(.path)**\n Line \(.line):" +
(.comments |
map(
if .in_reply_to_id then
" | \(.user.login): \(.body)"
else
" (\(.user.login)): \(.body)"
end
) |
join("\n")) + "\n"
) |
join("\n")
'
The formatted command produces output like:
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.