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
SkillScore86Maintained
Automatic
◆Coding pack
Last verified 8/29/2026
What it changes
Passed 19 of 22 test cases with the skill, and 12 of 22 without it.
Without skill55%
With skill86%
Checks it passed that the model alone missed
The draft avoids performative pleasantries.
The draft contains no social validation phrases.
The draft contains no performative pleasantries.
and 5 more in the full report
9 fixed10 passed either way1 still failing2 broke
Pass-rate lift
+32 pp
Tokens
-13%
Agent turns
0%
Response time
-33%
Model gemini-3.6-flashMeasured 8/29/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 9
Prompt
A reviewer noted: "The Redis lock key in `distributed_lock.py` needs a TTL to prevent deadlock if the worker dies." Compose a response confirming the update.
What was checked, without and with the skill
Checked
Without skill
With skill
The draft restates the requirement to add a TTL to the Redis lock key in distributed_lock.py.
Passed
Passed
The draft does not include performative phrases such as "Great point".
Missed
Passed
case-13 · gemini-3.6-flash · 8/29/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md59 linessingle file
Code Review Reception
Overview
Code review requires technical evaluation, not emotional performance.
Core principle: Verify before implementing. Ask before assuming. Technical correctness over social comfort.
The Response Pattern
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