skills.rest
LerianStudio
LerianStudioOFFICIAL
Explore all skills by this author →
Website𝕏@lerianstudioGitHub

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

205|26|Updated Oct 30, 2025
Search Tags:#workflow#development#quality assurance#code review#feedback#technical communication#self-management
One-click install
npx skills add https://github.com/LerianStudio/ring --skill receiving-code-review-lerianstudio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/LerianStudio/ring/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/LerianStudio/ring --skill receiving-code-review-lerianstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Receiving code review feedback can lead to performative agreement or blind implementation, potentially introducing new bugs or ignoring valid technical constraints. This skill enforces technical rigor and verification.

Core Features & Use Cases

  • Verify Before Implement: Mandates a structured process to read, understand, verify, and evaluate feedback before implementing.
  • No Performative Agreement: Explicitly forbids "You're absolutely right!" or "Thanks!" responses, focusing on technical acknowledgment or action.
  • Pushback Guidance: Provides clear reasons and methods for pushing back on technically questionable, context-lacking, or YAGNI-violating feedback.

Quick Start

I've received code review feedback. Use the receiving-code-review skill to process it.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I evaluate code review feedback before implementing it?▼

Code review feedback evaluation requires reading it completely, restating or asking for clarification, verifying suggestions against your codebase, assessing technical soundness for your specific context, and responding with technical acknowledgment or reasoned pushback before implementing changes one at a time with tests.

When should I push back on code review feedback?▼

Push back when feedback lacks context, violates YAGNI principles, or contradicts technical constraints specific to your codebase. Provide clear technical reasons for disagreement and engage in discussion rather than performative agreement.

What's the risk of implementing code review feedback without verification?▼

Blind implementation can introduce new bugs, ignore valid technical constraints, or embed misunderstood requirements. Verification before acting prevents these problems and maintains code quality and team alignment.

How do I respond to code review feedback technically?▼

Respond with technical acknowledgment of the feedback's merits or concrete pushback with reasoning, avoiding performative phrases like 'You're absolutely right.' Ground responses in your codebase's specific constraints and design decisions.

Should I implement multiple code review suggestions at once?▼

No. Implement changes one at a time, adding accompanying tests for each change. This isolates the impact of each suggestion and makes it easier to identify if a change introduces problems.

Related Skills

Explore More Software Engineering Skills→
obraobra
41

Code Review Reception

Evaluate and implement code review feedback with technical verification.

Community
Basic
tahatms12tahatms12

seo-plan

Plan SEO strategies with competitive analysis and implementation roadmaps for websites.

Community
Advanced
mouseqiao85mouseqiao85
1

requesting-code-review

Request code reviews with precise context and commit range integration.

Community
Intermediate
srbhrsrbhr
28.1k

receiving-code-review

Guide engineers through code-review feedback using a six-step response pattern.

Community
Basic