receiving-code-review
以技术严谨性处理代码审查反馈
也可从以下获取: obra,Cygnusfear,Cycleaddict,DYAI2025,davila7,ZhanlinCui,CodingCossack
代码审查需要技术评估，而非情感表演。此技能指导 AI 助手在实施前验证反馈、提出澄清问题，并在建议技术上不合理时提供有理由据的反对意见。
下载技能 ZIP
在 Claude 中上传
前往 设置 → 功能 → 技能 → 上传技能
开启并开始使用
测试它
正在使用“receiving-code-review”。 Reviewer: Remove the legacy code path for old API versions
预期结果:
Checking compatibility requirements... Build target is 10.15+, but this API needs 13+. The legacy path is still needed for backward compatibility. However, the current implementation has the wrong bundle ID. I can fix the bundle ID or we can drop pre-13 support. Which direction do you prefer?
正在使用“receiving-code-review”。 Reviewer: Fix items 1-6 in the PR
预期结果:
I understand items 1, 2, 3, and 6. I need clarification on items 4 and 5 before implementing. Can you elaborate on what changes you're looking for on those two items?
正在使用“receiving-code-review”。 Reviewer: Add proper error handling with retry logic and exponential backoff
预期结果:
Fixed. Added Try/Catch with retry logic (3 attempts, exponential backoff starting at 100ms) to the API call in api_service.rb:42-58. Tests pass.
安全审计
安全Static analysis flagged 24 instances of backtick patterns and 4 blocker patterns, but all are FALSE POSITIVES. The skill file (SKILL.md) is documentation-only markdown containing instructional text for AI behavior. No executable code, network calls, file operations, or cryptographic functions exist. The backtick patterns are markdown code blocks showing workflow examples, not shell execution. Blocker patterns are misidentified text fragments in documentation.
质量评分
你能构建什么
AI 助手接收人类审查
AI 助手接收来自人类开发者的代码审查反馈，需要确定哪些项目需要实施、哪些需要澄清，以及哪些需要用技术理由反对。
初级开发者学习审查响应
初级开发者学习如何以技术严谨性回应高级开发者反馈，而不是表演性同意，在盲目实施前验证建议。
外部贡献者处理维护者反馈
外部贡献者接收项目维护者的反馈，需要在实施前评估建议是否符合项目架构。
试试这些提示
I received code review feedback with 6 items. I understand items 1, 2, 3, and 6, but need clarification on items 4 and 5 before proceeding. Can you explain what changes you're looking for on those specific items?
Your suggestion to remove the legacy compatibility layer would break support for macOS 10.15. The current implementation targets 10.15+ but uses APIs that need 13+. Should I fix the bundle ID to maintain backward compatibility, or drop pre-13 support entirely?
The reviewer suggested implementing full metrics tracking with database storage, date filters, and CSV export. I searched the codebase and found no callers for this endpoint. Should I remove it following YAGNI, or is there usage I'm missing?
I pushed back on your suggestion, but after checking the test results you were correct. My understanding was wrong because I missed the integration test failure. Implementing the fix now.
最佳实践
- 在实施任何更改前始终针对实际代码库验证反馈
- 逐个实施更改并分别测试以尽早发现回归
- 当建议会破坏现有功能时用技术推理反对
避免
- 在验证反馈前说'你完全正确！'或'好观点！'
- 盲目实施反馈而不检查是否会破坏现有功能
- 实施项目 1-3 和 6 而跳过不明确的项目 4-5 而不先询问