skills.rest
flosrn
flosrnCOMMUNITY
Explore all skills by this author →
𝕏@flo_srnGitHub

receiving-code-review

Verify and implement code review feedback with reasoned technical responses.

Updated Aug 6, 2025
Search Tags:#code review#feedback#collaboration#implementation#verification#technical rigor
One-click install
npx skills add https://github.com/flosrn/.claude --skill receiving-code-review-flosrn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/flosrn/.claude/tree/main/skills/receiving-code-review
Command: npx skills add https://github.com/flosrn/.claude --skill receiving-code-review-flosrn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you handle code review feedback constructively and technically, ensuring that suggestions are understood, verified, and implemented correctly, rather than leading to performative agreement or blind implementation.

Core Features & Use Cases

  • Structured Response Pattern: Follows a clear process of reading, understanding, verifying, evaluating, responding, and implementing feedback.
  • Handling Ambiguity: Provides clear steps for seeking clarification on unclear feedback.
  • External Reviewer Scrutiny: Outlines a rigorous verification process for feedback from external sources.
  • YAGNI Principle: Integrates the "You Ain't Gonna Need It" principle to avoid unnecessary implementations.
  • Graceful Correction: Guides on how to correct your own pushback if you were mistaken.

Quick Start

When receiving code review feedback, verify each item against the codebase reality before implementing any suggestions.

Frequently Asked Questions about receiving-code-review

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

FAQPage Schema
How do I handle code review feedback without just blindly implementing suggestions?▼

Handle code review feedback by following a structured methodology of reading, understanding, verifying, evaluating, and responding to suggestions before implementation. This ensures feedback is technically sound and contextually appropriate for your codebase rather than met with performative agreement.

What is the best way to ask for clarification on unclear code review comments?▼

The best way to ask for clarification on unclear code review comments is to follow explicit steps for handling ambiguity. This involves seeking clarification directly from the reviewer to ensure you fully understand the technical suggestion before attempting any implementation.

How do I verify code review feedback from external reviewers?▼

Verify code review feedback from external reviewers through a rigorous technical verification process. You must scrutinize and validate each external suggestion against the codebase reality to ensure it is technically sound before implementing any changes.

When should I apply the YAGNI principle to code review suggestions?▼

Apply the YAGNI principle to code review suggestions when evaluating feedback to avoid unnecessary implementations. This ensures that you only implement technically sound and contextually appropriate changes, rejecting features or refactors that you are not going to need.

How do I gracefully correct my pushback if I was wrong about a code review comment?▼

Correct your pushback gracefully by acknowledging the technical mistake and implementing the feedback correctly. A structured response methodology guides you on how to recognize when you are mistaken and transition to implementing the technically sound suggestion.

Related Skills

Explore More Software Engineering Skills→
Threat-Vector-SecurityThreat-Vector-Security
11

receiving-code-review

Evaluate code-review feedback for technical accuracy before implementing changes.

Official
Intermediate
alexsandrocruzalexsandrocruz
6

receiving-code-review

Verify code review feedback against the codebase before implementing changes.

Community
Basic
galangryandanagalangryandana
20

receiving-code-review

Verify code-review feedback against the codebase before implementing changes.

Community
Basic
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic