receiving-code-review

What This Skill Does

The receiving-code-review skill acts as a rigorous technical filter for incoming code feedback. Instead of defaulting to passive agreement, it forces the AI to evaluate feedback against the specific codebase context and technical requirements. This skill enforces a 'verify-first' mindset, ensuring that the AI acts as a collaborative engineer rather than an automaton. It eliminates performative language like 'Great point' or 'You're absolutely right', replacing them with objective technical acknowledgments, verified restatements of requirements, and reasoned pushback when feedback is technically unsound or misaligned with project goals.

Installation

To install this skill, run the following command in your terminal or via the OpenClaw management console:

clawhub install openclaw/skills/skills/chenleiyanquan/receiving-code-review

Use Cases

1. Refactoring Reviews: When external reviewers suggest 'best practice' refactors that may violate YAGNI principles or introduce unnecessary abstraction into a lightweight codebase.
2. Security & Logic Patches: Ensuring complex logic changes suggested by team members are fully understood and verified against edge cases before applying them to core production systems.
3. Conflicting Requirements: Managing feedback from multiple stakeholders where a reviewer's suggestion might inadvertently break decisions made by your primary human partner.
4. Unclear Instruction Sets: Preventing partial implementations by identifying ambiguity early and pausing the workflow to seek explicit clarification before any code is modified.

Example Prompts

1. 'Review the feedback provided by the senior lead on my latest PR. Verify if the proposed architectural changes actually improve performance or if they add unnecessary complexity to our existing logic.'
2. 'I have received a list of 5 suggestions from the external auditor. Process them using the code-review skill: clarify anything ambiguous first, then implement only the high-priority security fixes.'
3. 'A team member suggested we implement a formal validation layer for this API endpoint. Check if the endpoint is currently in use. If it isn't, suggest removal instead of validation.'

Tips & Limitations

• Be Skeptical: Treat all external feedback as a hypothesis that must be tested against the codebase reality. Use grep or relevant code-search tools to verify if the code being discussed is even in active use.
• Maintain Context: Always verify if a proposed change has side effects on other components. If the code is complex, prioritize safety and request a discussion with your human partner before committing changes.
• Avoid Performative Language: The skill strictly prohibits phrases like 'Let me implement that now'. Always state your intent or ask for confirmation to ensure full alignment with project requirements. The primary goal is technical rigor, not speed of agreement.