receiving-code-review
以技術嚴謹性處理程式碼審查回饋
Também disponível em: DYAI2025,sickn33,CodingCossack,Cygnusfear,obra,davila7,ZhanlinCui
程式碼審查回饋需要技術驗證,而非盲目實作。此技能指導 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 says to add TypeScript strict mode to this file
Resultado esperado:
Checking tsconfig.json... Project uses strict:false globally. Enabling strict mode for one file creates inconsistency and may break existing type assumptions. Should we enable strict mode project-wide or keep current configuration?
A utilizar "receiving-code-review". Fix items 1-5 from the code review
Resultado esperado:
Understand items 1, 2, and 5. Need clarification on items 3 and 4: Item 3 mentions refactoring the auth flow but does not specify which approach. Item 4 references a shared utility that does not exist in the codebase. Please clarify before proceeding.
A utilizar "receiving-code-review". Implement proper pagination with cursor-based navigation
Resultado esperado:
- Grepped codebase for calls to this endpoint... No usage found.
- This is an unused API route. Remove it per YAGNI principle?
- Or is there planned usage I am missing?
Auditoria de Segurança
SeguroThis is a pure documentation skill providing guidance on code review feedback handling. All 36 static findings are false positives: C2 keywords are movie quotes, cryptographic patterns are markdown file extensions, backticks are documentation code blocks, and URLs are legitimate GitHub references. No actual code execution or network access.
Pontuação de qualidade
O Que Você Pode Construir
外部拉取請求審查
透過檢查技術正確性、與現有架構的相容性以及潛在的破壞性變更,評估來自外部貢獻者的建議,然後再接受變更。
團隊程式碼審查處理
處理團隊審查中的多項回饋,首先釐清不明確的項目,驗證技術可行性,並按優先順序實作變更並進行個別測試。
YAGNI 原則執行
透過驗證程式碼庫中的實際使用情況來挑戰功能擴展建議,並反駁實作未使用功能以避免違反 YAGNI 原則。
Tente Estes Prompts
I received code review feedback suggesting to extract this function into a utility module. Verify if this pattern is used elsewhere in the codebase before implementing.
Pull request has 8 review comments. Items 1-3 and 7-8 are clear. Need clarification on items 4, 5, and 6 regarding the database migration approach before proceeding with any implementation.
Reviewer suggests removing backward compatibility code for iOS 12. Check deployment targets and actual device support before implementing - we may still need this for enterprise customers.
Code review suggests implementing comprehensive error reporting with database logging, email notifications, and dashboard UI. Grep the codebase to verify if this error handler is actually called anywhere before building all this infrastructure.
Melhores Práticas
- 在實作變更前,始終針對實際程式碼庫狀態驗證回饋
- 在開始任何實作前,釐清多項目審查中的所有不明確項目
- 在反駁建議時使用技術推理和具體證據
Evitar
- 使用表演性同意回應,例如「完全正確」或「好觀點」,而不進行驗證
- 在不檢查破壞性變更或衝突的情況下立即實作建議
- 當某些回饋項目不明確時仍繼續進行部分實作
Perguntas Frequentes
此技能與接受所有審查回饋有何不同?
何時應該反駁程式碼審查回饋?
如果我無法輕易驗證某個建議怎麼辦?
如何處理多項目審查中的不明確項目?
此技能中提到的 YAGNI 檢查是什麼?
此技能是否適用於 GitHub 拉取請求工作流程?
Detalhes do Desenvolvedor
Autor
CycleaddictLicença
MIT
Repositório
https://github.com/Cycleaddict/generic-superpowers/tree/main/skills/receiving-code-reviewReferência
main
Estrutura de arquivos
📄 SKILL.md