skills.rest
cristoslc
cristoslcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

receiving-code-review

Evaluate code review feedback against codebase reality before implementation.

Updated Feb 22, 2026
Search Tags:#code review#feedback#implementation#verification#technical rigor#pushback
One-click install
npx skills add https://github.com/cristoslc/tidegate --skill receiving-code-review-cristoslc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/cristoslc/tidegate/tree/main/.agents/skills/receiving-code-review
Command: npx skills add https://github.com/cristoslc/tidegate --skill receiving-code-review-cristoslc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that code review feedback is technically evaluated and verified before implementation, preventing performative agreement and blind adherence to potentially incorrect suggestions.

Core Features & Use Cases

  • Verification Protocol: Implements a step-by-step process to understand, verify, and evaluate feedback against the codebase.
  • Reasoned Pushback: Provides clear guidelines on how and when to push back on feedback with technical reasoning.
  • Handling Ambiguity: Offers strategies for seeking clarification on unclear feedback to ensure correct implementation.
  • Use Case: When a reviewer suggests a change, this Skill guides you to first check if the suggestion is technically sound for the current codebase, if it breaks existing functionality, or if it aligns with project YAGNI principles, before committing to implementation.

Quick Start

When receiving code review feedback, follow the response pattern: read, understand, verify, evaluate, respond, and implement one item at a time.

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 changes?▼

Evaluating code review feedback requires reading, understanding, verifying, and evaluating the suggestion against your codebase reality and project context before responding or implementing. This prevents performative agreement and blind adherence to incorrect suggestions.

What is the best way to push back on incorrect code review suggestions?▼

The best way to push back on incorrect code review suggestions is to provide clear technical reasoning. Verify the suggestion against codebase reality, technical soundness, and project context like YAGNI principles, then respond with your reasoned technical evaluation.

How do I handle ambiguous code review comments during software development?▼

Handling ambiguous code review comments involves seeking clarification to ensure correct implementation. Following a structured response pattern allows you to address unclear feedback one item at a time before committing to any code changes.

When should I verify code review feedback against my codebase?▼

You should verify code review feedback against your codebase immediately upon receiving it. Check if the suggestion is technically sound, breaks existing functionality, or aligns with project YAGNI principles before committing to implementation to prevent blind adherence.

Why does performative agreement cause problems in code reviews?▼

Performative agreement causes problems in code reviews because it leads to implementing potentially incorrect suggestions without technical evaluation. Rigorously verifying feedback against codebase reality and technical soundness ensures correctness and prevents blind adherence to reviewer suggestions.

Can I process multiple code review feedback items at once?▼

Processing code review feedback should be done one item at a time. Managing the reception and technical evaluation of feedback requires a structured response pattern: read, understand, verify, evaluate, respond, and implement each suggestion individually.

Related Skills

Explore More Software Engineering Skills→
anipatkeanipatke
1

receiving-code-review

Evaluate and clarify code review feedback against the current codebase.

Community
Intermediate
RheasilviaRheasilvia

test-driven-development

Enforce the Red-Green-Refactor cycle with automated tests via terminal.

Community
Advanced
musher-devmusher-dev

shaping-reviewing-codebase-fit

Validate architectural sketch assumptions against an existing codebase.

Official
Advanced
benjgradbenjgrad

receiving-code-review

This is a test string.

Community
Intermediate