Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →getcrew44/requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Passed 18 of 21 test cases with the skill, and 11 of 21 without it.
and 8 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 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to identify the commit boundaries to send to a subagent code reviewer. Someone suggested using `git diff HEAD~1..HEAD > diff.patch` and sending the raw patch file. What exact commands should be run to capture the starting and ending revision identifiers for the reviewer parameters?
| Checked | Without skill | With skill |
|---|---|---|
| Runs git rev-parse to determine commit hashes rather than dumping diff patch files | Passed | Passed |
| Assigns the previous commit hash to BASE_SHA | Missed | Passed |
The instructions your model reads when the skill loads.
Dispatch a 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 general-purpose type, fill template at code-reviewer.md
Placeholders:
{DESCRIPTION} - Brief summary of what you built{PLAN_OR_REQUIREMENTS} - What it should do{BASE_SHA} - Starting commit{HEAD_SHA} - Ending commit3. Act on feedback:
test cases passed, vs 11 / 21 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.