Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/review-pr
Review a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation.
Passed 12 of 19 test cases with the skill, and 9 of 19 without it.
and 3 more in the full report
6 fixed9 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the very first step in the PR review procedure after setting up task tracking?
| Checked | Without skill | With skill |
|---|---|---|
| Executes $fetch-pr-comments as step 1. | Missed | Passed |
The instructions your model reads when the skill loads.
Fetch PR context, run a comprehensive code review, evaluate findings, and dispatch accepted findings to implementation.
At the start, use update_plan to track each step, restating any remaining steps of a parent workflow alongside them:
$fetch-pr-comments skill$review-code skill$evaluate-findings skill$resolve-findings skill$fetch-pr-comments SkillRun the $fetch-pr-comments skill to get unresolved review comments.
Detect the PR's base branch via gh pr view --json baseRefName --jq '.baseRefName', then run git fetch origin <base-branch> to bring the remote ref up to date.
$review-code SkillRun the $review-code skill. The diff command is git diff origin/<base-branch>...HEAD. Take the base from origin/: a local branch of the same name can sit behind the remote, which puts the merge base before an already-merged pull request and pulls merged work into the review as if it were new.
$evaluate-findings SkillRun the $evaluate-findings skill on the combined results from Step 3. Include any unresolved PR comments from Step 1 as additional findings for evaluation.
$resolve-findings SkillIf zero actionable findings survive evaluation, report that the code looks clean and stop.
Otherwise, run the $resolve-findings skill on the accepted findings from Step 4.
test cases passed, vs 9 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.