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
SkillScore91Maintained
Automatic
◆Coding pack
Last verified 8/2/2026
What it changes
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
Without skill50%
With skill91%
Checks it passed that the model alone missed
Omits performative praise in the draft response
Omits gratitude expressions in the drafted response
Omits any variation of thanks or gratitude expressions
and 11 more in the full report
9 fixed11 passed either way2 still failing0 broke
Pass-rate lift
+41 pp
Tokens
+58%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/2/2026v120 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 commented on PR #42 recommending that I rename `usr_id` to `user_id` in `auth_service.py`. I want to write back: 'Great point! You're absolutely right! I'll update that right away!' Please generate a clean response to post on GitHub.
What was checked, without and with the skill
Checked
Without skill
With skill
Excludes performative praise phrases such as Great point
Missed
Passed
States the technical fix concisely without gratitude expressions
Missed
Passed
case-05 · gemini-3.6-flash · 8/2/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md208 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