receiving-code-review
Evaluate code review feedback with technical rigor
也可从以下获取: DYAI2025,CodingCossack,obra,Cycleaddict,sickn33,ZhanlinCui,Cygnusfear
AI assistants often implement code review feedback without verification. This skill ensures technical evaluation of suggestions, asking clarifying questions and pushing back when feedback is unclear or technically incorrect.
下载技能 ZIP
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
开启并开始使用
测试它
正在使用“receiving-code-review”。 Reviewer suggested removing legacy API code and adding proper metrics tracking
预期结果:
- Checking legacy API usage - grep shows 3 call sites for backward compat (OS 10.15+)
- Suggesting clarification: verify if metrics endpoint is actually called before implementing
- Will clarify scope before implementing either change
安全审计
安全Pure prompt-based skill containing only markdown documentation for AI behavior during code review feedback reception. No executable code, scripts, network calls, filesystem access, or external command execution. The static findings from the secondary scan are FALSE POSITIVES caused by the scanner misinterpreting markdown code fences (backticks) as shell backtick execution and documentation references as cryptographic or network threats.
风险因素
🌐 网络访问 (1)
⚙️ 外部命令 (23)
质量评分
你能构建什么
Technical verification of suggestions
Ensure AI assistants verify code review feedback against codebase before implementing, preventing blind agreement
Consistent review handling
Maintain technical rigor when AI agents process external code review feedback from contributors
Quality feedback validation
Prevent AI assistants from implementing questionable suggestions without proper technical evaluation
试试这些提示
I am receiving code review feedback. Read all items completely. For each item: restate the requirement in my own words, verify against the codebase, and evaluate if technically sound. Ask clarification on unclear items before implementing anything.
External reviewer suggested: [suggestion]. Before implementing: check if this is technically correct for this codebase, if it breaks existing functionality, and if the reviewer understands the full context. Push back with technical reasoning if needed.
Reviewer suggests adding a feature. First grep the codebase to verify actual usage. If unused, suggest removal (YAGNI). If used, then implement properly. Report findings before proceeding.
I received N items of feedback. Identify any unclear items. Do NOT implement partial changes. State what I understand and what needs clarification before touching any code.
最佳实践
- Verify suggestions against actual codebase usage before implementing
- Ask clarifying questions on any unclear feedback items before proceeding
- Use technical reasoning when pushing back, not defensiveness
避免
- Blindly implementing feedback without verification
- Using performative agreement ('You are absolutely right')
- Implementing partial items when some are unclear
- Avoiding pushback on technically incorrect suggestions