Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jamditis/requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Passed 22 of 25 test cases with the skill, and 17 of 25 without it.
and 2 more in the full report
5 fixed17 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.
I am looking for the subagent request template file for code reviews in our repository structure. Where is this template file located?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies code-reviewer.md as the subagent template file location. | Missed | Passed |
The instructions your model reads when the skill loads.
Dispatch pr-review-toolkit:code-reviewer subagent to catch issues before they cascade. The reviewer gets precisely crafted context for evaluation, never your session's history. This keeps the reviewer focused on the work product, not your thought process, and preserves your own context for continued work.
Core principle: Review early, review often.
Mandatory:
Optional but valuable:
1. Get git SHAs:
BASE_SHA=$(git rev-parse HEAD~1) # or origin/main
HEAD_SHA=$(git rev-parse HEAD)
2. Dispatch code-reviewer subagent:
Use Task tool with pr-review-toolkit:code-reviewer type, fill template at code-reviewer.md
Placeholders:
{WHAT_WAS_IMPLEMENTED} - What you just builttest cases passed, vs 17 / 25 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.