{"id":"5e2f081b-e447-4b04-b6e2-78dd7ca3e6cd","shortId":"eUNG2P","kind":"skill","title":"receiving-code-review","tagline":"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","description":"# Code Review Reception\n\n## Overview\n\nCode review requires technical evaluation, not emotional performance.\n\n**Core principle:** Verify before implementing. Ask before assuming. Technical correctness over social comfort.\n\n## The Response Pattern\n\n```\nWHEN receiving code review feedback:\n\n1. READ: Complete feedback without reacting\n2. UNDERSTAND: Restate requirement in own words (or ask)\n3. VERIFY: Check against codebase reality\n4. EVALUATE: Technically sound for THIS codebase?\n5. RESPOND: Technical acknowledgment or reasoned pushback\n6. IMPLEMENT: One item at a time, test each\n```\n\n## Forbidden Responses\n\n**NEVER:**\n- \"You're absolutely right!\" (explicit CLAUDE.md violation)\n- \"Great point!\" / \"Excellent feedback!\" (performative)\n- \"Let me implement that now\" (before verification)\n\n**INSTEAD:**\n- Restate the technical requirement\n- Ask clarifying questions\n- Push back with technical reasoning if wrong\n- Just start working (actions > words)\n\n## Handling Unclear Feedback\n\n```\nIF any item is unclear:\n  STOP - do not implement anything yet\n  ASK for clarification on unclear items\n\nWHY: Items may be related. Partial understanding = wrong implementation.\n```\n\n**Example:**\n```\nyour human partner: \"Fix 1-6\"\nYou understand 1,2,3,6. Unclear on 4,5.\n\n❌ WRONG: Implement 1,2,3,6 now, ask about 4,5 later\n✅ RIGHT: \"I understand items 1,2,3,6. Need clarification on 4 and 5 before proceeding.\"\n```\n\n## Source-Specific Handling\n\n### From your human partner\n- **Trusted** - implement after understanding\n- **Still ask** if scope unclear\n- **No performative agreement**\n- **Skip to action** or technical acknowledgment\n\n### From External Reviewers\n```\nBEFORE implementing:\n  1. Check: Technically correct for THIS codebase?\n  2. Check: Breaks existing functionality?\n  3. Check: Reason for current implementation?\n  4. Check: Works on all platforms/versions?\n  5. Check: Does reviewer understand full context?\n\nIF suggestion seems wrong:\n  Push back with technical reasoning\n\nIF can't easily verify:\n  Say so: \"I can't verify this without [X]. Should I [investigate/ask/proceed]?\"\n\nIF conflicts with your human partner's prior decisions:\n  Stop and discuss with your human partner first\n```\n\n**your human partner's rule:** \"External feedback - be skeptical, but check carefully\"\n\n## YAGNI Check for \"Professional\" Features\n\n```\nIF reviewer suggests \"implementing properly\":\n  grep codebase for actual usage\n\n  IF unused: \"This endpoint isn't called. Remove it (YAGNI)?\"\n  IF used: Then implement properly\n```\n\n**your human partner's rule:** \"You and reviewer both report to me. If we don't need this feature, don't add it.\"\n\n## Implementation Order\n\n```\nFOR multi-item feedback:\n  1. Clarify anything unclear FIRST\n  2. Then implement in this order:\n     - Blocking issues (breaks, security)\n     - Simple fixes (typos, imports)\n     - Complex fixes (refactoring, logic)\n  3. Test each fix individually\n  4. Verify no regressions\n```\n\n## When To Push Back\n\nPush back when:\n- Suggestion breaks existing functionality\n- Reviewer lacks full context\n- Violates YAGNI (unused feature)\n- Technically incorrect for this stack\n- Legacy/compatibility reasons exist\n- Conflicts with your human partner's architectural decisions\n\n**How to push back:**\n- Use technical reasoning, not defensiveness\n- Ask specific questions\n- Reference working tests/code\n- Involve your human partner if architectural\n\n**Signal if uncomfortable pushing back out loud:** \"Strange things are afoot at the Circle K\"\n\n## Acknowledging Correct Feedback\n\nWhen feedback IS correct:\n```\n✅ \"Fixed. [Brief description of what changed]\"\n✅ \"Good catch - [specific issue]. Fixed in [location].\"\n✅ [Just fix it and show in the code]\n\n❌ \"You're absolutely right!\"\n❌ \"Great point!\"\n❌ \"Thanks for catching that!\"\n❌ \"Thanks for [anything]\"\n❌ ANY gratitude expression\n```\n\n**Why no thanks:** Actions speak. Just fix it. The code itself shows you heard the feedback.\n\n**If you catch yourself about to write \"Thanks\":** DELETE IT. State the fix instead.\n\n## Gracefully Correcting Your Pushback\n\nIf you pushed back and were wrong:\n```\n✅ \"You were right - I checked [X] and it does [Y]. Implementing now.\"\n✅ \"Verified this and you're correct. My initial understanding was wrong because [reason]. Fixing.\"\n\n❌ Long apology\n❌ Defending why you pushed back\n❌ Over-explaining\n```\n\nState the correction factually and move on.\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Performative agreement | State requirement or just act |\n| Blind implementation | Verify against codebase first |\n| Batch without testing | One at a time, test each |\n| Assuming reviewer is right | Check if breaks things |\n| Avoiding pushback | Technical correctness > comfort |\n| Partial implementation | Clarify all items first |\n| Can't verify, proceed anyway | State limitation, ask for direction |\n\n## Real Examples\n\n**Performative Agreement (Bad):**\n```\nReviewer: \"Remove legacy code\"\n❌ \"You're absolutely right! Let me remove that...\"\n```\n\n**Technical Verification (Good):**\n```\nReviewer: \"Remove legacy code\"\n✅ \"Checking... build target is 10.15+, this API needs 13+. Need legacy for backward compat. Current impl has wrong bundle ID - fix it or drop pre-13 support?\"\n```\n\n**YAGNI (Good):**\n```\nReviewer: \"Implement proper metrics tracking with database, date filters, CSV export\"\n✅ \"Grepped codebase - nothing calls this endpoint. Remove it (YAGNI)? Or is there usage I'm missing?\"\n```\n\n**Unclear Item (Good):**\n```\nyour human partner: \"Fix items 1-6\"\nYou understand 1,2,3,6. Unclear on 4,5.\n✅ \"Understand 1,2,3,6. Need clarification on 4 and 5 before implementing.\"\n```\n\n## GitHub Thread Replies\n\nWhen replying to inline review comments on GitHub, reply in the comment thread (`gh api repos/{owner}/{repo}/pulls/{pr}/comments/{id}/replies`), not as a top-level PR comment.\n\n## The Bottom Line\n\n**External feedback = suggestions to evaluate, not orders to follow.**\n\nVerify. Question. Then implement.\n\nNo performative agreement. Technical rigor always.","tags":["receiving","code","review","dolu","agents","skills","dolutech","agent-skills","opencode"],"capabilities":["skill","source-dolutech","skill-receiving-code-review","topic-agent-skills","topic-opencode","topic-skills"],"categories":["dolu-agents-skills"],"synonyms":[],"warnings":[],"endpointUrl":"https://skills.sh/dolutech/dolu-agents-skills/receiving-code-review","protocol":"skill","transport":"skills-sh","auth":{"type":"none","details":{"cli":"npx skills add dolutech/dolu-agents-skills","source_repo":"https://github.com/dolutech/dolu-agents-skills","install_from":"skills.sh"}},"qualityScore":"0.453","qualityRationale":"deterministic score 0.45 from registry signals: · indexed on github topic:agent-skills · 6 github stars · SKILL.md body (5,990 chars)","verified":false,"liveness":"unknown","lastLivenessCheck":null,"agentReviews":{"count":0,"score_avg":null,"cost_usd_avg":null,"success_rate":null,"latency_p50_ms":null,"narrative_summary":null,"summary_updated_at":null},"enrichmentModel":"deterministic:skill-github:v1","enrichmentVersion":1,"enrichedAt":"2026-05-18T19:14:40.403Z","embedding":null,"createdAt":"2026-05-18T13:22:09.950Z","updatedAt":"2026-05-18T19:14:40.403Z","lastSeenAt":"2026-05-18T19:14:40.403Z","tsv":"'-13':738 '-6':187,778 '/comments':825 '/pulls':823 '/replies':827 '1':66,186,190,200,214,257,403,777,781,790 '10.15':717 '13':721 '2':72,191,201,215,264,408,782,791 '3':81,192,202,216,269,426,783,792 '4':87,196,207,221,275,431,787,797 '5':94,197,208,223,281,788,799 '6':101,193,203,217,784,793 'absolut':115,536,700 'acknowledg':97,251,506 'act':644 'action':150,248,553 'actual':356 'add':394 'afoot':501 'agreement':29,245,639,692,854 'alway':857 'anyth':164,405,546 'anyway':683 'api':719,819 'apolog':618 'architectur':468,490 'ask':50,80,137,166,205,239,479,686 'assum':52,660 'avoid':668 'back':141,293,438,440,473,495,587,623 'backward':725 'bad':693 'batch':651 'blind':31,645 'block':414 'bottom':837 'break':266,416,443,666 'brief':514 'build':714 'bundl':731 'call':364,756 'care':342 'catch':520,542,568 'chang':518 'check':83,258,265,270,276,282,341,344,595,664,713 'circl':504 'clarif':168,219,795 'clarifi':138,404,675 'claude.md':118 'code':3,8,33,37,63,533,559,697,712 'codebas':85,93,263,354,649,754 'comfort':57,672 'comment':810,816,835 'common':634 'compat':726 'complet':68 'complex':422 'conflict':315,462 'context':287,449 'core':45 'correct':54,260,507,512,581,608,629,671 'csv':751 'current':273,727 'databas':748 'date':749 'decis':322,469 'defend':619 'defens':478 'delet':574 'descript':515 'direct':688 'discuss':325 'drop':736 'easili':300 'emot':43 'endpoint':361,758 'especi':14 'evalu':41,88,843 'exampl':181,690 'excel':122 'exist':267,444,461 'explain':626 'explicit':117 'export':752 'express':549 'extern':253,336,839 'factual':630 'featur':347,391,453 'feedback':10,16,65,69,123,154,337,402,508,510,565,840 'filter':750 'first':330,407,650,678 'fix':185,419,423,429,513,523,527,556,578,616,637,733,775 'follow':847 'forbidden':110 'full':286,448 'function':268,445 'gh':818 'github':802,812 'good':519,708,741,771 'grace':580 'gratitud':548 'great':120,538 'grep':353,753 'handl':152,229 'heard':563 'human':183,232,318,328,332,374,465,487,773 'id':732,826 'impl':728 'implement':12,32,49,102,127,163,180,199,235,256,274,351,371,396,410,601,646,674,743,801,851 'import':421 'incorrect':455 'individu':430 'initi':610 'inlin':808 'instead':132,579 'investigate/ask/proceed':313 'involv':485 'isn':362 'issu':415,522 'item':104,157,171,173,213,401,677,770,776 'k':505 'lack':447 'later':209 'legaci':696,711,723 'legacy/compatibility':459 'let':125,702 'level':833 'limit':685 'line':838 'locat':525 'logic':425 'long':617 'loud':497 'm':767 'may':174 'metric':745 'miss':768 'mistak':635,636 'move':632 'multi':400 'multi-item':399 'need':218,389,720,722,794 'never':112 'noth':755 'one':103,654 'order':397,413,845 'over-explain':624 'overview':36 'owner':821 'partial':177,673 'partner':184,233,319,329,333,375,466,488,774 'pattern':60 'perform':28,44,124,244,638,691,853 'platforms/versions':280 'point':121,539 'pr':824,834 'pre':737 'principl':46 'prior':321 'proceed':225,682 'profession':346 'proper':352,372,744 'push':140,292,437,439,472,494,586,622 'pushback':100,583,669 'question':21,139,481,849 're':114,535,607,699 'react':71 'read':67 'real':689 'realiti':86 'reason':99,144,271,296,460,476,615 'receiv':2,7,62 'receiving-code-review':1 'recept':35 'refactor':424 'refer':482 'regress':434 'relat':176 'remov':365,695,704,710,759 'repli':804,806,813 'repo':820,822 'report':382 'requir':22,39,75,136,641 'respond':95 'respons':59,111 'restat':74,133 'review':4,9,34,38,64,254,284,349,380,446,661,694,709,742,809 'right':116,210,537,593,663,701 'rigor':24,856 'rule':335,377 'say':302 'scope':241 'secur':417 'seem':17,290 'show':530,561 'signal':491 'simpl':418 'skeptic':339 'skill' 'skill-receiving-code-review' 'skip':246 'social':56 'sound':90 'sourc':227 'source-dolutech' 'source-specif':226 'speak':554 'specif':228,480,521 'stack':458 'start':148 'state':576,627,640,684 'still':238 'stop':160,323 'strang':498 'suggest':13,289,350,442,841 'support':739 'target':715 'technic':20,23,40,53,89,96,135,143,250,259,295,454,475,670,706,855 'test':108,427,653,658 'tests/code':484 'thank':540,544,552,573 'thing':499,667 'thread':803,817 'time':107,657 'top':832 'top-level':831 'topic-agent-skills' 'topic-opencode' 'topic-skills' 'track':746 'trust':234 'typo':420 'unclear':18,153,159,170,194,242,406,769,785 'uncomfort':493 'understand':73,178,189,212,237,285,611,780,789 'unus':359,452 'usag':357,765 'use':5,369,474 'verif':26,131,707 'verifi':47,82,301,307,432,603,647,681,848 'violat':119,450 'without':70,309,652 'word':78,151 'work':149,277,483 'write':572 'wrong':146,179,198,291,590,613,730 'x':310,596 'y':600 'yagni':343,367,451,740,761 'yet':165","prices":[{"id":"c71de993-9c17-48d4-b30a-3d83cbbc8520","listingId":"5e2f081b-e447-4b04-b6e2-78dd7ca3e6cd","amountUsd":"0","unit":"free","nativeCurrency":null,"nativeAmount":null,"chain":null,"payTo":null,"paymentMethod":"skill-free","isPrimary":true,"details":{"org":"dolutech","category":"dolu-agents-skills","install_from":"skills.sh"},"createdAt":"2026-05-18T13:22:09.950Z"}],"sources":[{"listingId":"5e2f081b-e447-4b04-b6e2-78dd7ca3e6cd","source":"github","sourceId":"dolutech/dolu-agents-skills/receiving-code-review","sourceUrl":"https://github.com/dolutech/dolu-agents-skills/tree/main/skills/receiving-code-review","isPrimary":false,"firstSeenAt":"2026-05-18T13:22:09.950Z","lastSeenAt":"2026-05-18T19:14:40.403Z"}],"details":{"listingId":"5e2f081b-e447-4b04-b6e2-78dd7ca3e6cd","quickStartSnippet":null,"exampleRequest":null,"exampleResponse":null,"schema":null,"openapiUrl":null,"agentsTxtUrl":null,"citations":[],"useCases":[],"bestFor":[],"notFor":[],"kindDetails":{"org":"dolutech","slug":"receiving-code-review","github":{"repo":"dolutech/dolu-agents-skills","stars":6,"topics":["agent-skills","opencode","skills"],"license":"mit","html_url":"https://github.com/dolutech/dolu-agents-skills","pushed_at":"2026-03-21T12:00:55Z","description":"Dolu Agents Skills - Open-source collection of modular and extensible skills for AI agents.","skill_md_sha":"4ea72cdf014d6b18223e4248ed9444bd3953445a","skill_md_path":"skills/receiving-code-review/SKILL.md","default_branch":"main","skill_tree_url":"https://github.com/dolutech/dolu-agents-skills/tree/main/skills/receiving-code-review"},"layout":"multi","source":"github","category":"dolu-agents-skills","frontmatter":{"name":"receiving-code-review","description":"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"},"skills_sh_url":"https://skills.sh/dolutech/dolu-agents-skills/receiving-code-review"},"updatedAt":"2026-05-18T19:14:40.403Z"}}