receiving-code-review

Validate code review feedback against the codebase before implementation.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/JiangAustin/Money_Never_Sleep --skill receiving-code-review-jiangaustin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/JiangAustin/Money_Never_Sleep/tree/main/.claude/skills/receiving-code-review
Command: npx skills add https://github.com/JiangAustin/Money_Never_Sleep --skill receiving-code-review-jiangaustin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

当你收到代码审查意见时,这个 Skill 帮你先验证再实施,避免盲目接受不明确、错误或会破坏现有功能的建议。

Core Features & Use Cases

  • 复述和澄清审查反馈,先把范围和疑点问清楚。
  • 对照代码库实际实现判断建议是否合理,必要时用技术理由反驳。
  • 按阻塞问题、简单修复、复杂修复的顺序逐项处理并验证回归。
  • 适用于同事评审、外部 PR 评论、与既有架构冲突的修改建议,以及 YAGNI 判断。

Quick Start

当你收到一条代码审查意见时,先用这个 Skill 帮我验证它是否合理,并给出该怎么回应和实施的建议。

Frequently Asked Questions about receiving-code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code review feedback before implementing changes?

Handling code review feedback requires validating suggestions against the actual codebase before implementation. You should clarify ambiguous comments, prioritize blockers over simple and complex fixes, and use technical justification to rebut incorrect suggestions during refactoring or bug fixes.

What is the best way to handle conflicting code review comments on a GitHub PR?

Handling conflicting code review comments involves clarifying the scope first, then validating each suggestion against the actual codebase. You process items stepwise by priority, using technical justification to accept, refactor, or rebut conflicting feedback regarding safety issues or architectural changes.

How do I validate ambiguous refactoring suggestions from external reviewers?

Validating ambiguous refactoring suggestions requires checking the proposed changes against your actual codebase implementation. Clarify unclear items with the reviewer first, then implement stepwise while verifying regressions, using technical justification if the external feedback violates YAGNI principles or existing architecture.

When should I reject code review feedback instead of implementing it?

You should reject code review feedback when suggestions conflict with existing architecture, violate YAGNI decisions, or introduce safety issues. Provide a technical justification rebuttal after validating the comment against the actual codebase, rather than blindly accepting incorrect external review suggestions.

Can I use this approach for both internal peer reviews and external PR comments?

Yes, you can use this validation approach for both internal peer reviews and external PR comments. The process applies to ambiguous, external, or conflicting review feedback across bug fixes, refactors, and safety issues, ensuring you verify all suggestions against the codebase before implementation.