receiving-code-review
以技術嚴謹性評估程式碼審查回饋
Também disponível em: DYAI2025,sickn33,CodingCossack,Cygnusfear,obra,ZhanlinCui,Cycleaddict
AI 助理經常在未經驗證的情況下實作程式碼審查回饋。此技能確保對建議進行技術性評估,提出澄清問題,並在回饋不明確或技術上不正確時提出質疑。
Baixar o ZIP da skill
Upload no Claude
Vá em Configurações → Capacidades → Skills → Upload skill
Ative e comece a usar
Testar
A utilizar "receiving-code-review". Reviewer suggested removing legacy API code and adding proper metrics tracking
Resultado esperado:
- 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
Auditoria de Segurança
SeguroPure 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.
Fatores de risco
🌐 Acesso à rede (1)
⚙️ Comandos externos (23)
Pontuação de qualidade
O Que Você Pode Construir
建議的技術驗證
確保 AI 助理在實作前根據程式碼庫驗證程式碼審查回饋,防止盲目同意
一致的審查處理
當 AI 代理處理來自貢獻者的外部程式碼審查回饋時,維持技術嚴謹性
品質回饋驗證
防止 AI 助理在未進行適當技術評估的情況下實作可疑建議
Tente Estes Prompts
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.
Melhores Práticas
- 在實作前根據程式碼庫的實際使用情況驗證建議
- 在繼續進行之前,對任何不明確的回饋項目提出澄清問題
- 提出質疑時使用技術理由,而非防禦心態
Evitar
- 未經驗證就盲目實作回饋
- 使用表演性同意(「您說得完全正確」)
- 在某些項目不明確時實作部分項目
- 對技術上不正確的建議避免提出質疑