receiving-code-reviev1.0.0

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.