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
SkillScore65Maintained
Automatic
◆Coding pack
Last verified 8/30/2026
What it changes
Passed 15 of 23 test cases with the skill, and 11 of 23 without it.
Without skill48%
With skill65%
Checks it passed that the model alone missed
The comment contains no performative praise of the reviewer.
The response contains no expressions of gratitude such as thanks or thank you.
The response begins with the exact phrase 'Receiving Code Review skill activated.'
and 7 more in the full report
8 fixed7 passed either way4 still failing4 broke
Pass-rate lift
+17 pp
Tokens
+42%
Agent turns
0%
Response time
-25%
Model gemini-3.6-flashMeasured 8/30/2026v115 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
A code reviewer found an off-by-one error in array_utils.cpp line 42. We verified that changing < to <= fixes the boundary condition test. Write the exact comment to post on the PR.
What was checked, without and with the skill
Checked
Without skill
With skill
The comment states the bug fix location and change factually without saying thanks or thank you.
Passed
Passed
The comment contains no performative praise of the reviewer.
Missed
Passed
case-20 · gemini-3.6-flash · 8/30/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md210 linessingle file
Code Review Reception
Overview
Announce at start: "Receiving Code Review skill activated."
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