receiving-code-reviewUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Install via ClawdBot CLI:
clawdbot install chenleiyanquan/receiving-code-reviewGrade Good — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated Mar 1, 2026
When a developer receives vague feedback like 'Fix items 1-6' with unclear details, they must pause implementation, ask for clarification on ambiguous items, and avoid partial fixes to prevent errors. This ensures technical accuracy and prevents wasted effort.
In a team using external code reviewers, this skill helps verify suggestions against the codebase's context, check for breaking changes, and push back with technical reasoning if needed, ensuring compatibility and avoiding unnecessary features.
When a reviewer suggests adding 'professional' features like enhanced metrics, the skill prompts checking actual usage in the codebase. If unused, it recommends removal to adhere to YAGNI, saving development time and resources.
If a developer incorrectly pushes back on valid feedback, this skill guides them to acknowledge the error factually, explain the verification process, and implement the fix without over-apologizing, maintaining professionalism and efficiency.
For complex reviews with multiple items, the skill enforces clarifying unclear points first, then prioritizing fixes by severity (e.g., blocking issues before simple typos), and testing each individually to prevent regressions and ensure quality.
This skill supports SaaS teams by ensuring code reviews focus on technical correctness over social comfort, reducing bugs and technical debt. It helps maintain scalable codebases through rigorous verification and YAGNI checks, improving product reliability.
For agencies delivering custom software, the skill aids in handling client or external feedback skeptically, verifying suggestions against project requirements, and pushing back when necessary to avoid scope creep and ensure deliverables meet specifications.
In open source projects, this skill helps maintainers process community feedback by checking technical soundness, ensuring compatibility across platforms, and avoiding performative agreements, fostering a collaborative yet rigorous development environment.
💬 Integration Tip
Integrate this skill into code review workflows by training teams to follow the response pattern and avoid forbidden responses, using tools like GitHub comments for structured feedback.
Scored Apr 15, 2026
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Control and operate Opencode via slash commands. Use this skill to manage sessions, select models, switch agents (plan/build), and coordinate coding through Opencode.
Ship production code with AI agents through acceptance contracts, micro diffs, red green loops, and deterministic handoff checkpoints.
A comprehensive skill for using the Cursor CLI agent for various software engineering tasks (updated for 2026 features, includes tmux automation guide).
Provides a 7-step debugging protocol plus language-specific commands to systematically identify, verify, and fix software bugs across multiple environments.