Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jnmetacode/receiving-code-review
收到代码审查反馈后、实施建议之前使用,尤其当反馈不明确或技术上有疑问时——需要技术严谨性和验证,而非敷衍附和或盲目执行
Passed 21 of 22 test cases with the skill, and 9 of 22 without it.
and 12 more in the full report
12 fixed9 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Draft a response acknowledging a reviewer's recommendation to update a legacy helper method, keeping the response concise and compliant with repository communication guidelines.
| Checked | Without skill | With skill |
|---|---|---|
| The draft contains no expressions such as 'You are totally right!' or 'You're completely right!' | Passed | Passed |
| The response describes the technical change directly without praise | Missed | Passed |
The instructions your model reads when the skill loads.
代码审查需要的是技术评估,不是情绪表演。
核心原则: 先验证再实施。先提问再假设。技术正确性优先于社交舒适度。
收到代码审查反馈时:
1. 阅读:完整阅读反馈,不急于反应
2. 理解:用自己的话复述需求(或提问)
3. 验证:对照代码库的实际情况检查
4. 评估:对这个代码库来说技术上合理吗?
5. 回应:技术性确认或有理有据的反驳
6. 实施:一次一项,逐个测试
绝不要说:
应该这样做:
如果有任何一项不明确:
停下来——先不要实施任何内容
就不明确的项目提出澄清
test cases passed, vs 9 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.