receiving-code-review

Evaluate code review feedback for technical soundness before implementation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/pearjelly/turbooknow --skill receiving-code-review-pearjelly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: receiving-code-review
Source: https://github.com/pearjelly/turbooknow/tree/main/.agent/skills/receiving-code-review
Command: npx skills add https://github.com/pearjelly/turbooknow --skill receiving-code-review-pearjelly

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 changes, especially from external sources.

Core Features & Use Cases

  • Structured Response: Follows a clear pattern: Read, Understand, Verify, Evaluate, Respond, Implement.
  • Verification Focus: Emphasizes checking feedback against codebase reality and technical soundness.
  • Handling Ambiguity: Provides clear steps for seeking clarification on unclear feedback.
  • External Feedback Scrutiny: Includes specific checks for external reviewer suggestions (technical correctness, impact on existing functionality, context understanding).
  • YAGNI Principle: Integrates the "You Ain't Gonna Need It" principle for feature suggestions.
  • Graceful Correction: Defines how to correct pushback if proven wrong.

Quick Start

When receiving code review feedback, verify its technical soundness against the codebase 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 verify code review feedback before implementing changes?

Verify code review feedback by applying a structured pattern: Read, Understand, Verify, Evaluate, Respond, and Implement. This ensures you check technical soundness against the codebase before making any modifications.

What is the best way to handle ambiguous code review comments?

Handling ambiguous code review comments requires seeking clarification through defined steps. You should verify the feedback against codebase reality and request specific details to ensure technical accuracy before proceeding.

How do I apply the YAGNI principle to pull request feedback?

Apply the YAGNI principle to pull request feedback by evaluating feature suggestions to ensure they are immediately necessary. This prevents unnecessary additions based on external reviewer recommendations that lack current context.

How do I correct pushback from a reviewer when I am proven right?

Correct pushback from a reviewer by following a graceful correction process. When technical verification proves your existing implementation is sound, respond with the verified evidence rather than blindly agreeing to changes.

Why should I avoid performative agreement during developer workflow code reviews?

Avoiding performative agreement during developer workflow code reviews prioritizes technical rigor. Blind implementation of feedback, especially from external sources, can introduce errors that contradict codebase reality and break existing functionality.