Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →guanyang/receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Passed 19 of 22 test cases with the skill, and 10 of 22 without it.
and 9 more in the full report
11 fixed8 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
A code review comment points out a misspelled variable name `usrName` on line 12. Draft the comment reply after renaming it to `userName`.
| Checked | Without skill | With skill |
|---|---|---|
| Output describes the fix directly without gratitude expressions. | Missed | Passed |
The instructions your model reads when the skill loads.
Code review requires technical evaluation, not emotional performance.
Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.
WHEN receiving code review feedback:
1. READ: Complete feedback without reacting
2. UNDERSTAND: Restate requirement in own words (or ask)
3. VERIFY: Check against codebase reality
4. EVALUATE: Technically sound for THIS codebase?
5. RESPOND: Technical acknowledgment or reasoned pushback
6. IMPLEMENT: One item at a time, test each
NEVER:
INSTEAD:
IF any item is unclear:
STOP - do not implement anything yet
ASK for clarification on unclear items
test cases passed, vs 10 / 22 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.